Page Builder Templates and Elements: Four Words, Four Different Jobs

Every page builder's marketing uses the word "template," and almost none of them mean quite the same thing by it. Sometimes it's a full pre-written page with stock content already on it. Sometimes it's just a color scheme. Sometimes, confusingly, it's both at once, with no way to get one without the other. This builder draws that line in a specific, consistent place — and the word "template" here is deliberately the narrowest of four different layers, not the broadest.

Photo by Karl Abuid on Unsplash

The word doing four jobs at once

Here, in order from broadest visual effect to most specific: a page template sets the chrome — background, card shadow, corner radius, whether text reads light or dark. Style knobs sit on top of that, adjusting the same handful of chrome properties per form without changing which template is selected. A preset is a separate, third thing: a ready-made starting combination of a template, a set of style-knob values, and an actual list of content blocks, bundled together for convenience. And the blocks themselves — headings, images, pricing tables, and the rest — are the only layer that holds real content and, for most of them, their own individual color and alignment. Four layers, one page, and conflating any two of them is the single easiest way to go looking for a setting in the wrong place.

What actually earns the name here

A page template is exactly eight fixed options — clean, gradient, dark, minimal, hero, ocean, sunset, glass — and every one of them controls chrome only: the page and card background, the card's shadow and corner radius, and whether the template's own title and subtitle text render light or dark. None of them decide what's actually written on the page, what images appear, or how many sections it has. Switching from clean to dark restyles the frame a page's content sits inside without touching the content itself — closer to choosing a picture frame than to choosing a photo.

The dial, and the two things it was never allowed to touch

Style knobs — accent color, page background, card background, card radius, card border, card shadow, and a light-text toggle — exist specifically to adjust a chosen template's own chrome properties per form, without switching templates outright. Two things were deliberately tried as knobs here and then pulled back out, worth knowing because both are common assumptions coming from other builders. Title and subtitle color was briefly a global knob; it was removed because a page-wide color override quietly reskinned every text block at once, including ones that already had their own color set individually — title and subtitle color now comes from the selected template alone, full stop, and a specific element needing a different color is a block-level decision instead. A page-wide alignment switch existed too, forcing every header block to the same side at once; it was removed in favor of setting alignment per block, which is what makes a left-aligned logo next to a centered heading possible on the same page. Neither removal was an oversight — both are a style knob staying scoped to the template's own chrome, not reaching down into content it was never meant to touch.

The closest thing to what most people mean by "template"

If the word "template" conjures a finished-looking page rather than an empty frame, the layer actually being pictured is a preset. Twenty of them exist at the time of writing — among them Blank, Simple, Pricing plans, Agency intake, SaaS demo request, Real estate inquiry, Freelancer, Event, Store inquiry, Volunteer & support, Job application, Coaching consultation, Waitlist, Local business booking, Client onboarding, Support, Wedding RSVP, Insurance quote, Newsletter, and Feedback survey — and each one is a specific template choice, a specific set of style-knob values, and a specific starting block list, applied together in one step. Applying Wedding RSVP drops in a monogram-style heading and RSVP-shaped blocks on a template suited to it; applying Waitlist leans toward a badge and a short brief instead. Nothing about a preset is locked in afterward — every block it adds is exactly as editable as one added by hand, and applying a different preset later prompts a choice between merging it into what already exists or replacing the page outright.

Where color and alignment actually live instead

Individual blocks are where a specific element gets its own look, and not every block gets the same controls. Text-bearing blocks — a large heading, a shorter heading, a brief paragraph, plain text, a badge, a menu of links — each carry their own alignment, color, font size, font, and style (normal, italic, bold, or both), editable the moment that block is selected in the live preview. An image block gets alignment plus its own border style, width, and color, but no text color or font, for the obvious reason that an image has neither. A pricing table and an image-plus-text media card are both self-contained the other direction: neither exposes a per-block color or alignment field at all, since both are built as one fixed unit rather than a container of independently stylable parts — the media card's one layout-specific option instead is where its image sits relative to its text (top, bottom, left, right, or centered as a full- bleed background, which forces white text over a dark gradient scrim so it stays legible against whatever photo gets dropped in). A grid block holds other blocks in side-by-side columns, two to four of them, and is the one block that nests — though only one level deep, since a grid's own columns can't hold another grid.

Which one wins when two of them disagree

Put a color directly on a heading block, and that color wins over whatever the selected template would otherwise have supplied — a block's own setting always takes precedence over the template's default, never the other way around. Leave a block's color unset, and it falls back to the template's title or subtitle color exactly as if no override existed. Alignment works the same way, just with a different fallback: a block with no alignment chosen defaults to centered rather than inheriting anything. In practice, building a page usually means starting from a preset (which already has sensible values at every layer), swapping its template if the chrome needs to look different, nudging a style knob or two for a one-off color, and then reaching for a single block's own color or alignment field only for the one element that genuinely needs to stand apart from everything around it.

What this costs, and where it publishes

Designing a page — any template, any preset, any number of blocks, any amount of restyling — is free with no limit on how much gets changed before it goes live. Publishing it is a one-time 5 credits, deducted once and not tied to how many submissions the form behind it collects afterward; see pricing for how credits are purchased and spent elsewhere on an account. A published page lives on a your-choice.nbforms.com subdomain — there's no custom- domain option today, so a page that needs to sit on a domain already owned elsewhere is better served by embedding the same form into that site directly, covered in hosted form pages with no website. For what the editor looks like end to end, including why it deliberately has no drag-and-drop canvas, see the no-code landing page builder overview.