Understand existing Project and Lite Editor graph nodes and their embedded child-project behavior; these are not in the visual Add menu but remain in MCP create_node for compatibility.
Where: Open an existing Flowgen canvas and select its Project or Lite Editor node; these legacy entries are not available for new Add-menu authoring.
Key ideas
- Project node: A real f0 child project (website/video) inside the graph; connected inputs inject into its assets; outputs a render.
- Lite Editor node: A single-page editor; outputs standalone HTML + CSS and a bundle you can re-edit in another node.
Steps
- Locate the Project or Lite Editor node on the canvas; these types are absent from the current visual Add menu.
- If an external MCP host must maintain a compatibility workflow, create_node still accepts project and liteEditor on the currently open Flowgen canvas; this does not create a standalone Dashboard project.
- Inspect its connected inputs and saved outputs before opening the embedded child editor; projectType simple/video is locked after the child is created.
- Use the focused Project or Lite guide for each socket contract and save lifecycle, then verify the outputs after saving.
- For new website editing, choose the current Website Editor or Unified Section. For native timeline/compositing, choose the separate Video Editor node.
Current API and UI status
- Project and Lite Editor remain API-compatible create_node types but are not offered in the visual Add catalog.
- Project exposes html_out, css_out, bundle_out, image_out, and pages_out; Lite Editor exposes html_out, css_out, and bundle_out.
- For a new standalone project, use Dashboard. Flowgen create_node adds only to the currently connected graph.
Related guides
- Project node: embedded Website or Video child project
- Lite Editor node: embedded single-page child editor
- Website Editor node: an editable website document inside Flowgen
- Create an editable website section in Flowgen
- Flowgen Video Editor node: native composition inputs, editor surface, outputs, persistence, and MCP