H1Projects
Status: hub for project-level content, publishing, and nested operational surfaces.
This folder maps to the main project routes and nested feature surfaces:
/projects/projects/[projectId]/projects/[projectId]/assistant/projects/[projectId]/documents/projects/[projectId]/documents2/projects/[projectId]/offers/projects/[projectId]/orders/projects/[projectId]/products/projects/[projectId]/trips/projects/[projectId]/assets
H2Current status
- Projects act as the parent shell for content, documents, offers, orders, products, trips, and assistant surfaces.
- The project area is where the codebase behaves like a reusable internal platform.
- It is an umbrella surface, not a single business entity.
- Project documents and project sections are schema-backed and should be documented carefully because they connect to many child systems.
H2Key schema entities
ProjectProjectSectionProjectUserProjectCollaboratorProjectContactProjectStoryProjectPostProjectDocumentProjectAsset
H2Archive notes
- older project-level notes live in
archive/ - move superseded umbrella planning and done-notes there instead of deleting them
H2Folder rule
- Keep project-level platform notes here.
- If a child entity becomes complex, give it its own hub and keep project notes as the umbrella surface.