Projects
Page Goal
Help users understand the project organization model in Temps and how to structure their applications effectively. Enable users to make informed decisions about organizing their deployments.
Target Persona
Organizer Olivia - A developer or team lead who:
- Managing multiple applications or microservices
- Needs to organize deployments logically
- Working with a team (may need access controls)
- Planning how to structure their Temps workspace
- Values: Organization, clarity, scalability
- Questions: "How should I structure this?", "Can I group related apps?"
- Timeline: 5-10 minutes to understand the model
Key Content to Include
1. What is a Project
- Definition and purpose
- How projects group related applications
- Projects vs Applications distinction
2. Project Structure
- One project can contain multiple applications
- Shared settings across project apps
- Environment inheritance
3. Use Cases
- Single project per client
- Monorepo deployments
- Microservices architecture
- Team workspaces
4. Creating Projects
- How to create a project
- Naming conventions
- Project settings
5. Managing Projects
- Adding applications to projects
- Project-level environment variables
- Team access and permissions
- Project settings and configuration
6. Best Practices
- When to create a new project vs new application
- Organizing for teams
- Scaling considerations
Success Metrics
- User understands what projects are
- User knows when to create a new project
- User can organize their applications logically
- User understands relationship between projects and applications