Blame
|
1 | # Projects |
||||||
| 2 | ||||||||
|
3 | Projects are the primary containers for work, integrations, products, experiments, and ecosystem deliverables. |
||||||
|
4 | |||||||
|
5 | <div class="docs-section-heading"> |
||||||
| 6 | <h2>Project model</h2> |
|||||||
| 7 | <p>Use projects to group resources, collaborators, settings, and operational history.</p> |
|||||||
| 8 | </div> |
|||||||
|
9 | |||||||
|
10 | A project may be a game, app, API integration, research effort, studio build, community tool, or internal system. Projects usually live inside [[Organizations]] and use [[Teams]] and [[Permissions]] to manage access. |
||||||
| 11 | ||||||||
| 12 | ## Project contents |
|||||||
| 13 | ||||||||
| 14 | - Name, description, and ownership. |
|||||||
| 15 | - Members, teams, and roles. |
|||||||
| 16 | - API credentials or integration settings. |
|||||||
| 17 | - Environments such as development, staging, and production. |
|||||||
| 18 | - Links to docs, repos, support channels, or dashboards. |
|||||||
| 19 | ||||||||
| 20 | ## Project lifecycle |
|||||||
| 21 | ||||||||
| 22 | 1. Create project and assign ownership. |
|||||||
| 23 | 2. Add teams or collaborators. |
|||||||
| 24 | 3. Configure integrations and environments. |
|||||||
| 25 | 4. Document security and operational notes. |
|||||||
| 26 | 5. Archive or transfer when work ends. |
|||||||
| 27 | ||||||||
| 28 | <div class="docs-grid"> |
|||||||
| 29 | <a class="docs-card" href="/Organizations">Organizations</a> |
|||||||
| 30 | <a class="docs-card" href="/Teams">Teams</a> |
|||||||
| 31 | <a class="docs-card" href="/Permissions">Permissions</a> |
|||||||
| 32 | <a class="docs-card" href="/Studio">Studio</a> |
|||||||
| 33 | </div> |
|||||||