Understand exactly which legacy HTML nodes were retired, why existing flows still work, what replaces each node, and how to migrate without confusing the current Unified Section/Agentic Web node with the retired HTML Section type.
Where: Existing saved Flowgen graphs containing HTML Section or HTML Page Join/HTML Combine
Key ideas
- Only two legacy types are retired here: HTML Section (HTML_SECTION) and HTML Page Join/HTML Combine (HTML_JOIN) are removed from current creation surfaces. Unified Section (UNIFIED_SECTION), shown as Agentic Web and Interactive element, remains the current editable section node.
- Retired does not mean broken: Existing saved graphs still register, rehydrate, render, and run these nodes. Compatibility is preserved so an old production flow does not disappear merely because its creation tile was removed.
- New assembly stays editable: Use Agentic Web/Interactive element to create native section documents, then connect editor_out directly into Website Studio page inputs. Website Studio preserves each section as an ordered editable component without a flattening join.
- HTML Export is the delivery step: After Website Studio assembles the editable document, HTML Export creates one final HTML file per page. It does not replace section authoring or page assembly.
Steps
- Identify the actual node type in the old graph: HTML Section generates one legacy section; HTML Page Join/Combine stacks legacy HTML; Agentic Web/Interactive element is the current Unified Section and should not be removed as “retired.”
- If the legacy flow is working and no revision is needed, leave it intact. Run a representative input and record the current outputs before any migration.
- Replace a legacy HTML Section with Agentic Web (or Interactive element when that preset matches the job). Reconnect prompt, references/assets, Design System, source HTML/CSS, and downstream consumers using the current typed sockets.
- Open the new Section editor and verify the editable document result, responsive layout, motion/interaction capabilities, and html_out/editor_out outputs.
- Replace HTML Page Join/Combine by connecting the ordered Section editor_out values directly to the intended Website Studio page socket. Connect the Design System to Website Studio’s own design_system_in.
- Open Website Studio and confirm every section appears once and in the intended order. Save/close so the newest document returns to the node.
- Reconnect downstream consumers to Website Studio’s bundle/HTML outputs and run them one stage at a time.
- When delivery files are required, add HTML Export after Website Studio and export/test every page.
- Remove the old nodes only after the replacement graph has been saved, reopened, and verified end to end.
Retirement matrix
- HTML Section / HTML_SECTION — retired creation path; replace with Agentic Web/Interactive element (UNIFIED_SECTION).
- HTML Page Join / HTML Combine / HTML_JOIN — retired creation path; replace assembly with direct ordered inputs into Website Studio.
- Unified Section / UNIFIED_SECTION — current; Add labels Agentic Web and Interactive element.
- Website Studio / DOCUMENT_EDITOR simple mode — current multi-page assembly/editor.
- HTML Export / HTML_EXPORT — current final-file exporter.
Where retired nodes were removed
- Add catalog.
- Canvas/noodle creation suggestions.
- AI create_node enum and planning instructions.
- New blueprints/templates.
Where compatibility remains
- NodeType registration and saved-graph rehydration.
- Existing edges and outputs.
- Legacy website feed recognition inside current agents/runners.
- The old node’s own card/properties when an existing graph contains it.
Tips
- Migrate one legacy boundary at a time and compare output before deleting anything.
- Prefer editor_out/bundle connections when editability matters; use html_out only for consumers that truly need a flattened value.
- Do not add a legacy join back into a current Website Studio flow.
Limitations and important notes
- Some old graphs depend on legacy socket aliases; verify every edge after replacement.
- A flattened legacy HTML result cannot automatically recover the original editable section boundaries.
- Retirement removes creation paths but is not a promise that compatibility will remain forever; migrate actively maintained flows.
Troubleshooting
I cannot find HTML Section or HTML Combine in Add
That is intentional. Use Agentic Web/Interactive element for the section and Website Studio for ordered assembly.
Search says Unified Section is retired
That wording is stale. Only HTML_SECTION is retired; UNIFIED_SECTION remains current under Agentic Web and Interactive element.
The migrated page has duplicate sections
Remove the old join feed after direct section inputs are connected; do not feed both the combined legacy page and its individual sections into the same page.
Website Studio has the right sections but downstream output is old
Save/close the embedded editor, confirm its node version changed, then rerun the downstream render/export.
FAQ
Will opening an old graph delete its retired nodes?
No. They still rehydrate for compatibility.
Was Agentic Web retired?
No. Agentic Web and Interactive element are current presets of UNIFIED_SECTION.
Should every old flow be migrated immediately?
Not solely for appearance. Prioritize flows that are actively edited, republished, or need current section/editor capabilities.