single-page
Diya Trivedicreate a project to buidl simple single page design
Comments (0)
Sign in to leave a comment
Project Tasks
20 planning tasksGenerate system requirement document
Generate personas & user flows
Create flow for Designer
Landing
Fix Landing review findings: Q1 as reviewed now: Fixed navbar obscures the hero eyebrow… (+2 more)
Landing / Navigation
Landing / Split Hero
Landing / Single Page Constraint Band
Landing / Workflow Band
Landing / Start Band
Landing / Footer
Navigation
Footer
Sign Up
Login
Projects
Project Editor
Preview
Architecture
Workspace task plan
</h1></p></a></a>// one page per projectexport default LandingPage;One project holds exactly one single-page design.
A project in single-page is built around a single page. You compose its content and layout once, and that composition is what you review. The product does not build multi-page sites, page collections, or page hierarchies — the constraint is the product.
If you need a second page, that is a second project. Same constraint, same workflow, cleanly separated.
- Create a project01Every design begins as a project. One project holds one single page — no page collection, no hierarchy.
- Compose in the Project Editor02The Editor is a split pane: the page canvas on one side, its structure on the other, both live as you work.
- Review in Preview03Preview renders the finished page exactly as composed, so the result can be read before it is kept.
A project, a page, and the structure under it
Work moves through one project at a time: create the project, compose the single page in the Project Editor where the composition and its structure sit side by side, then review the result in Preview. Nothing is published and no second page is added — the project holds the one page it was made for.
Begin your single page.
Create a project, compose one page, and see it as a design and as structure.
</h1></p></a></a>// one page per projectexport default LandingPage;One project holds exactly one single-page design.
A project in single-page is built around a single page. You compose its content and layout once, and that composition is what you review. The product does not build multi-page sites, page collections, or page hierarchies — the constraint is the product.
If you need a second page, that is a second project. Same constraint, same workflow, cleanly separated.
- Create a project01Every design begins as a project. One project holds one single page — no page collection, no hierarchy.
- Compose in the Project Editor02The Editor is a split pane: the page canvas on one side, its structure on the other, both live as you work.
- Review in Preview03Preview renders the finished page exactly as composed, so the result can be read before it is kept.
A project, a page, and the structure under it
Work moves through one project at a time: create the project, compose the single page in the Project Editor where the composition and its structure sit side by side, then review the result in Preview. Nothing is published and no second page is added — the project holds the one page it was made for.
Begin your single page.
Create a project, compose one page, and see it as a design and as structure.
No comments yet. Be the first!