---
title: "raw.tt Template"
url: "https://docs.chinaski.net/en/theming/raw-tt/"
type: "page"
language: "en"
description: "Use the raw.tt page template when the page body should be emitted verbatim as the full HTML file: when to choose it, and what still applies inside."
updated: "2026-09-29"
generated: "Markdown rendition of the HTML page at url, built by Chinaski"
---

# raw.tt Template

`raw.tt` is the “total control” page template: whatever you type in the page body is emitted **verbatim** as the built HTML file. No head, no header, no footer, no theme CSS, no theme wrapper: you author the complete document.

## When to choose it

- A page that should be *your markup, your document*: self-styled HTML shells, please-and-thank-you pages whose presentation is hand-built, tracking-only redirect pages, anything that must not inherit theme structure.
- Not for fragments. The body must be the full HTML (doctype, `<head>`, `<body>`) exactly as it will ship. Just that body, and nothing else, becomes the page.

## What still applies inside

- **`{{block:name​}}` shortcodes resolve normally**: you can assemble content from library blocks inside your hand-written markup.
- **Global and per-page head/body snippets inject only when your markup contains `</head>`/`</body>` tags**: a verification/analytics tag needs those anchors present, since insertion loops over those regions.

## What explicitly does not apply

- Breadcrumbs, featured image, stacks areas, and password gating: raw pages bypass themed features by design (`raw.tt` states that in its own header). The related editor fields still exist; they just don’t render.

## Selection and behavior

- Opt in per page from the template dropdown (it’s among the auto-discovered non-partial templates).
- The page still builds per language and occupies its normal URL/slug position; the built output is whatever you wrote.

## Safety

Raw output satisfies the same build checks as every other page: broken links, accessibility, and other pre-promotion quality signals are scanned; a raw page failing a promote-following check still blocks (like any other content). No graces beyond the standard pipeline.
