Landing Pages
Landing pages carry campaign-style content without the site’s usual chrome — headers, footers, menus are all deliberately absent. Chinaski ships two templates for this: landing.tt (an unbranded shell with self-contained block styling) and raw.tt (full hand-authored HTML). This page covers both.
The landing template
Pages selecting this template render with:
- No site branding — no header, footer, or navigation from the active theme, and theme CSS doesn’t load.
- The standard head — canonical, OpenGraph, hreflang, analytics, and consent gating via the shared meta partial; SEO values have all their usual page-level overrides.
- Neutral self-contained styling — the stylesheet that the template brings gives the block types (hero, CTA, stat, testimonial, and the rest of the shortcode families) reasonable default rendering that isn’t theme-dependent, so the landing page looks intentional in a browser even as the theme changes around it.
- Password gating — landing pages support the same protected-page mechanism as regular pages.
Select it per page from the page’s template dropdown, and pick a body content: the editor’s “Start from template…” list includes a landing preset (welcome heading, key benefits list, get-started CTA), after which page content is yours to author with blocks and normal rich text.
What’s appropriate inside
{{block:name}}shortcodes are the main building material — the block-resolved content carries the page body, so assembling a landing page means placing existing library blocks (or writing markup inline if you prefer).- Inline HTML in the body is stored verbatim wherever you write real markup; just keeping your landing body scoped to the container area.
The raw template
raw.tt is a peer to landing.tt for operatives who want total control: the page body is the complete HTML document you type (doctype, <head>, <body>), with no shell, no meta partial, and no theme CSS — deliberately bare. Block shortcodes still resolve, global/per-item head and body snippets inject when your markup contains matching </head>/</body> tags, and — distinctly — password gates and breadcrumb/featured-image/theme features intentionally do not apply.
Use landing.tt when a page needs to exist in the system as a real page with SEO values and protected access, but shouldn’t look like the site. Use raw.tt when the page IS custom markup and nothing else.
Differences at a glance
| landing.tt | raw.tt | |
|---|---|---|
| Provides document shell + head | yes | no (you write it) |
| Site header/footer | no | no |
| Block default styles | yes | no |
| Snippets | via the head partial | only when your markup contains those tags |
| Password gate | supported | not applicable |
| SEO/sharing tags | yes (standard) | only what you write |
| Body expectation | fragment | complete document |