Landing Page Creator: Four Real Pages From One Tool

A landing page creator is only as good as what comes out of it, and the fairest way to test one isn't to read its feature list — it's to point it at pages that have nothing to do with each other and see whether what comes out actually looks like different things. Below are four, built from presets that already exist in this one, with their exact starting content included rather than described in the abstract.

Photo by Mika Baumeister on Unsplash

A monogram, not a form embed

Applying the Wedding RSVP preset sets the page to the clean template, nudges its accent to a dusty rose (#b76e79), rounds the card corners to 24px, gives the card a subtle border, and tints the page background a pale pink (#fdf6f5). On top of that chrome, it drops in four blocks exactly as written: a serif heading reading "You're Invited," a large serif monogram ("A & J") at 56px, a brief line — "We would love to celebrate with you. Please RSVP by May 1." — in the same serif, and a divider. None of that is the form itself; it's the page content sitting above whatever fields the form was actually built with (a guest's name, whether they're attending, a meal choice) — the monogram and the invitation copy are what a visitor sees first, the fields are what they fill in after. The one edit nearly every couple makes immediately is obvious: the monogram initials and the RSVP-by date are the two details a preset can't guess, sitting right at the top where they're the first thing selected and retyped.

The one that looks like it shouldn't exist yet

The Waitlist preset reaches for the opposite end of the mood: the dark template, a violet accent (#8b5cf6), a strong card border, and a monospace font running through every text block — a badge reading "Early access," an h1 reading "Join the waitlist," a brief line about being first in line, a divider, and a menu with two links ("Follow updates," "Read the changelog"). Nothing about the underlying block types is different from the wedding page above — it's a badge, a heading, a brief, a divider, a menu, same as before — but a dark template plus a monospace font plus a violet accent reads as a product in private beta instead of an invitation, entirely through chrome and style-knob choices, not through different building blocks. A team that wants the same early-access structure without committing to a dark page isn't stuck with it either — dark is the preset's template choice, not a fixed part of "waitlist," so swapping it for glass or gradient keeps the exact same badge-and-menu blocks while changing the mood entirely.

A hero image before a single form field loads

The Job Application preset pairs the hero template with a blue accent (#1d4ed8), a subtle card border, and a pale blue page background, then opens with a small rounded company logo image (48px), a bold "We're hiring" badge, an h1 reading "Join the team," a line of body text about the open role, a divider, and a menu linking to "Open roles" and "Our culture." The image block here is doing a specific job the other two pages didn't need — establishing whose posting this is before a visitor reads a word of the role description, the same way a letterhead would on paper. Swapping in an actual company logo over the placeholder image is the one change that matters more than any text edit here, since a generic avatar undercuts "Join the team" in a way no amount of rewritten copy fixes on its own.

A gradient loud enough to interrupt a scroll

The SaaS Demo Request preset goes a different direction again: the gradient template, an indigo-to-pink page background set directly in the style knobs rather than left as a flat color, a bold "See it in action" h1, a "Book a live demo" badge, a brief line about a 30-minute walkthrough, a divider, and a menu linking to a 2-minute demo video and a pricing page. Where the wedding and job pages above lean on a calm, pale page background to let their content sit quietly on top, this one uses the page background itself as the attention-getting element — the gradient is doing work the other three presets deliberately left to their text instead.

What's still yours to write

None of the copy above is meant to survive to publishing unedited. "We would love to celebrate with you," "Be first in line when we launch," "We're looking for a senior designer to join our product team" — every line is a normal, editable text block that happens to start with placeholder wording, there to show where copy goes and roughly how much space it fills, not as a finished sentence someone already approved. A preset's actual job is deciding structure and chrome; the words are the one part of the page every one of these four examples still needs from whoever's actually publishing it. The same is true of the links inside each preset's menu block — every "Open roles," "Read the changelog," or "View pricing" in the four pages above points at example.com by default, a placeholder in exactly the same spirit as the wording around it, expecting to be swapped for a real URL before anything goes live rather than left pointing nowhere.

What's identical in all four

Underneath four pages that read nothing alike, the same four things are true of all of them: each is one preset selected once, not a sequence of manual adjustments; each remains exactly as editable afterward as a page built block-by-block from blank would have been — swap the template, recolor one block, delete the menu, nothing is locked by having come from a preset; each publishes to a your-choice.nbforms.com subdomain, with no custom-domain option for any of them; and each costs the same one-time 5 credits to actually go live, regardless of which preset or how many blocks got changed afterward — see pricing for how that cost fits into the rest of an account's credits. Changing course entirely afterward works the same way on any of the four: applying a different preset to a page that already has content prompts a choice between merging the new blocks in alongside what's there or replacing the page outright, so picking the wrong starting point isn't a reason to start over from a blank page.

For exactly what a template, a style knob, a preset, and a block each do and don't control, see templates and elements; for the editor itself end to end, including why there's no drag-and-drop canvas, see the no-code landing page builder overview.