Blame
|
1 | # Studio |
||||||
| 2 | ||||||||
|
3 | Studio is the creative and production workspace layer for building, organizing, and shipping AeThex-connected experiences. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Studio role</h2> |
|||||||
| 7 | <p>Studio connects creators, projects, teams, and platform services into a working production environment.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | Studio should be documented as a workspace, not just a product page. It belongs near [[Projects]], [[Teams]], [[GameForge]], [[Labs]], and [[Passport]]. |
||||||
| 11 | ||||||||
| 12 | ## Studio workflows |
|||||||
| 13 | ||||||||
| 14 | - Create and organize projects. |
|||||||
| 15 | - Invite collaborators and assign access. |
|||||||
| 16 | - Connect identity and platform services. |
|||||||
| 17 | - Track assets, builds, or experience metadata. |
|||||||
| 18 | - Move experiments from Labs toward production. |
|||||||
| 19 | ||||||||
| 20 | ## Related systems |
|||||||
| 21 | ||||||||
| 22 | - [[Projects]] for ownership and structure. |
|||||||
| 23 | - [[Teams]] for collaborators. |
|||||||
| 24 | - [[Permissions]] for access. |
|||||||
| 25 | - [[GameForge]] for game-oriented workflows. |
|||||||
| 26 | - [[Labs]] for prototypes and experiments. |
|||||||
| 27 | ||||||||
| 28 | <div class="docs-grid"> |
|||||||
| 29 | <a class="docs-card" href="/Projects">Projects</a> |
|||||||
| 30 | <a class="docs-card" href="/Teams">Teams</a> |
|||||||
| 31 | <a class="docs-card" href="/GameForge">GameForge</a> |
|||||||
| 32 | <a class="docs-card" href="/Labs">Labs</a> |
|||||||
| 33 | </div> |
|||||||