Landing page wizard

The Landing page wizard builds a one-page site in a single run: a short form, a “what will be created” plan — and a published page at your address. This reference covers the form fields, the four accent palettes, the twelve block toggles, and everything that appears in your project afterwards.

A one-page site is a header with anchors, a hero with an offer, a few content sections and a lead form. The Landing wizard assembles all of it from one form and publishes immediately: the page is live on the public domain as soon as the run finishes — there is no separate “deploy” step. Everything it creates stays a regular platform object — records, files and flows you can edit by hand.

Where to find the wizard

Admin → Site → the Flows tab → Create flow — a “What are we building?” gallery opens instead of a form; pick the Landing page card. The wizard doesn’t ask for a slug or address here: by default the page lands on /lp, and on a collision it takes the next free path without overwriting anything.

Form fields

Field	What to enter
Product name *	Becomes the hero headline
Offer — one sentence *	Hero subheadline
Button label	The hero call to action; defaults to “Leave a request”
Accent color	One of four palettes: indigo, emerald, graphite, amber
Block toggles (12)	Client logos, stats, features, about, how it works, gallery, pricing, testimonials, FAQ, team, final call to action, lead form
Page path	The landing’s address, `/lp` by default
SEO description	Goes into the meta description
Open Graph image	A link to the card shown in messengers and social networks

Fields without an asterisk ship with sensible defaults; only “Product name” and “Offer” are required.

There is no “site address” field — it isn’t needed: the wizard builds the canonical URL, og:url and structured data from the request host. The same content serves a subdomain and a custom domain without regeneration.

A toggled-off block is not a hidden section but a content type that is never created: the block lands neither in the project nor in the template. The toggle order sets the section order — the form reads like a table of contents. The lead form is the heaviest toggle: without it the wizard creates no “Landing form”, no “Landing leads” and no intake flow.

What the wizard creates

Before running, the wizard shows a “what will be created” plan — the exact list of operations it is about to perform. One click on “Create” adds to your project:

Artifact	Role
Up to 20 `landing-*` content types	“Landing page”, “Hero”, “Meta”, “SEO”, “Header”, “Menu items”, “Form”, “Sections” + one type per enabled block + “Landing leads”
Records holding your copy	The answers land as records in the CMS; block content starts from lorem placeholders — the template holds no texts
`landing.liquid` template + `landing.css` + `landing.js`	Markup, mobile-first layout, light and dark themes, OG meta, canonical, JSON-LD — in the Files tab
“Landing” flow	GET on the page path: three queries against the content, then template render; the response is cached for 5 minutes
“Landing leads” flow	POST to the same address: a honeypot against bots and required-field validation; each lead is stored as a record
Route	Binds the flow to the chosen path; page and form share one address

How it works

The page. The flow makes three content queries and renders landing.liquid; the main one fetches the “Landing page” record that assembles the whole site — every section holds links to its own content. Responses cache for 5 minutes, and record edits flush the cache themselves — saved content is live within a couple of seconds.

The form. Leads POST to the page’s own address: a honeypot field filters bots, required fields are validated before anything is stored. A lead lands in the “Landing leads” type and is read in the admin like any record; a redirect brings the visitor back.

SEO. The form’s image becomes og:image — links shared in messengers go out with a cover. The template ships OG and Twitter meta, a host-based canonical and structured data: WebSite always, FAQPage when the FAQ block is on.

Themes. The page follows the visitor’s system preference by default, with a manual toggle in the header — the choice is remembered.

After the run: edits and moves

Copy is edited in records — like any project content. Menu links are records of “Menu items”: adding or removing one is a single record. If the address stops working for you, change the path in the flow settings: the page moves, the old route is cleaned up, and a “Page moved: A → B” toast confirms it.

Running the wizard again on the same project does not touch existing records: a second run is for a fresh project, not for “refreshing” content.

Run it on a demo project first: on a clean project you risk nothing and can review the result at leisure — then repeat where the page is actually needed.

FAQ

Question	Answer
Do I need a developer?	No. The run — form and publish — happens entirely in the admin; edits afterwards go to records and files. You only open the template when you want to change the markup.
Where do I see leads?	Content → the “Landing leads” type — regular records with the form data.
Can I change the address after publishing?	Yes: change the path in the flow settings and the old route is cleaned up.
What happens if I run the wizard twice?	Existing records are untouched. You don’t need a re-run to update content.
I want another section or custom markup	The template and styles live in the Files tab (`landing.liquid`, `landing.css`) — edit them like any site file.