Overview
The canvas shows a branching registration graph—not a single linear form. It opens with Additional Comments (TEXTAREA), then splits toward Date of Birth (DATE) and Email Address (EMAIL) with visibility between nodes. Both paths feed Experience Level (Years) (PAGE), which branches again to Favorite Color (PAGE) and Full Name (TEXT). Full Name leads to Password (PAGE); Favorite Color and Password converge on Phone Number (TEL). After phone, Preferred Contact Time (PAGE) leads to Website (Optional) (PAGE).
How it works
- Start at Additional Comments; visibility gates which of Date of Birth or Email Address appears next in the runner experience.
- Experience Level (Years) sits where the upper and lower branches rejoin—typed as a PAGE step in the builder.
- A second split sends some users through Favorite Color and others through Full Name then Password, still using visibility on the connectors.
- Phone Number (TEL) is the merge point before Preferred Contact Time and the closing Website (Optional) step.
Key Features
- Rich type mix: TEXTAREA, DATE, EMAIL, TEXT, TEL, and multiple PAGE steps for grouped subflows.
- Two-level branching (after comments, after experience level) with a single TEL merge—matches how the graph reads left-to-right.
- Website (Optional) is explicitly optional in the node title, aligned with the canvas.
- Copy is scoped to the nodes and edge labels you see—no invented CRM or third-party integrations.
Use Cases
- Products that need optional commentary and contact preference without one giant static form.
- Demos where PMs walk stakeholders through the exact same node names as in /engines/user-registration.
- Teams extending the graph with more PAGE sections after Phone without rewriting the hero story.