Creating Partials
Partials are created as regular markdown files in your project structure. To create a partial, click the + button in the sidebar of a project and select “New Partial”. Then add the content you want to reuse to the partial.Referencing Partials
Reference partials in your markdown by using the{% partial %} tag.
/partial.
Path Resolution
file is a project-relative path. A leading slash means “from the project root”; without it, the path resolves relative to the page that’s referencing the partial.
pages/home, file="footer" would resolve to pages/footer (the page’s own directory) — almost certainly not what you want. Use the leading slash to make references unambiguous and resilient to the page being moved.
Legacy single-tree projects (no pages/ / partials/ / queries/ split) accept the bare form because there’s no relative-resolution layer there.
Naming Conventions
Partial filenames support letters, numbers, underscores, and hyphens. Names likemy_partial or my-partial are stored as you typed them, so the file you create in the sidebar matches the reference you write in markdown ({% partial file="my_partial" /%}) and the on-disk filename if your project is synced to GitHub.
Spaces are normalized to hyphens (My Partial → my-partial); other punctuation is stripped.
Variables
Partials have an isolated scope for variables. They can be defined in frontmatter, or passed as variables.Frontmatter
Partials can define their own variables using frontmatter at the top of the partial file:Passing Variables
You can pass variables to partials when referencing them. Variables of the same name will override those defined in the partial’s frontmatter.Scoping Rules
- Isolation: Partials cannot access variables from the parent page unless explicitly passed
- Precedence: Passed variables take precedence over frontmatter variables
- Fallback: If no variable is provided, the partial uses its frontmatter variable

