Understand Designer as a shared multi-page project, promote an editor-backed Flowgen node, edit it independently, and safely pull those changes back to the canvas.
Where: Dashboard → New project → Designer, or a Designer/editor-backed Flowgen card → Promote to project.
Before you start
- You need edit access to promote or change a project. Pulling changes back also requires access to the original Flowgen canvas.
Key ideas
- One document, many typed pages: A Designer project stores every page in one shared document. Each page has its own stable id, type, HTML, motion, comments, undo history, and active-page presence. Landing pages, video edits, ads, decks, motion, documents, wireframes, email, dashboards, logos, Media, and Design system pages can coexist without turning the project into separate files.
- Promotion preserves a relationship: Promoting a Designer, Website Editor, or Video Editor card creates a dashboard project linked to the source node. The card shows that link and can open the project again. The original canvas is not silently rewritten while someone works in the promoted project.
- Pull is an explicit merge boundary: Use Pull project edits when the promoted project should become the node’s new content. Flowmo checks that the relationship still points at the expected source and avoids replacing newer canvas work with a stale project snapshot. Collaborators can see who is active and which page each person is on.
Steps
- Create a Designer project directly, or open the menu on an eligible Flowgen editor card and choose Promote to project.
- Give the project a useful name and open it from the dashboard or the linked-project badge on the card.
- Add pages with Add page, choose the type that matches each deliverable, and rename/reorder pages before a large build.
- Edit one page at a time. Presence shows collaborators without forcing everyone onto the same active page; page-specific undo affects that page rather than another collaborator’s page.
- When the project is the source of truth, return to the original Flowgen card and choose Pull project edits. Review the changed-page summary before accepting it.
- Run downstream nodes again after a pull. Existing rendered artifacts are historical outputs and are not automatically recomputed.
The twelve current page types
- Landing page & website
- Reel & video edit
- Ad
- Slide deck
- Animation & motion
- Document & research
- Wireframe & mockup
- HTML email
- Live dashboard
- Logo
- Media
- Design system
Sharing and roles
- Project sharing uses project roles rather than an unscoped public editing switch.
- Presence and active-page indicators are collaborative awareness, not a lock: two editors can work on different pages.
- A viewer can navigate the page rail and presentation output without receiving edit permission.
- Show in Flowgen returns to the linked source when that relationship is still available.
Page and appearance continuity
Shared appearance settings now update across collaborating tabs, while the document-level page-loss guard reverses and names any non-user transaction that would empty a page. Removing an element also removes exposed fields that pointed inside it, preventing dead controls after collaborative or AI edits.
Tips
- Use page types as intent, not conversion. Changing a type changes the available workspace and defaults; it does not magically convert unrelated existing markup.
- Pull at a deliberate checkpoint, then render/test the affected downstream branch before more project edits accumulate.
Limitations and important notes
- Promotion is available only for supported editor-backed cards and does not turn every Flowgen node into a Designer project.
- The shared document carries pages, but external uploads and generated artifacts still need valid stored URLs for collaborators and exports.
- Legacy Designer kinds can open for compatibility but are no longer offered as new page types.
Troubleshooting
Pull project edits is unavailable or refuses the update.
Confirm that you opened the original linked node, still have edit permission, and did not replace or unlink it. Reopen the promoted project from the card badge so the relationship is resolved from current data.
A downstream node still shows the old version.
Pulling updates the editor-backed source; it does not rerun dependent nodes. Run the affected branch or final renderer again.