How content files work
File paths, frontmatter, layouts, and the page index.
On this page
Files become URLs
Loom discovers .vlt and .md files under the configured content pages root. By default this is user/content/pages.
| File relative to the pages root | URL |
|---|---|
hello.vlt |
/hello |
notes/hello.md |
/notes/hello |
docs/index.vlt |
/docs |
index occupies the parent URL. The special home handler loads welcome. Avoid two files that resolve to the same URL; discovery rejects ambiguous slugs.
Frontmatter is page data
---
title: A field note
status: published
layout: v2
excerpt: A short introduction to the page.
---
Frontmatter supplies the title, status, layout, dates, and other metadata. Pages default to draft. With debug mode disabled, the page controller returns 404 for unpublished pages.
Use trusted: true only for content you control that needs full Velvet template execution. Ordinary documentation does not need it. Template trust and publication status are separate decisions.
Markdown and Velvet
.md files are parsed as Markdown. .vlt files can mix content blocks such as @html, @markdown, and @text.
@html
<h1>A page in a file.</h1>
@markdown
This paragraph uses **Markdown**.
A layout is a view under user/views/layouts. The application can supply its own content and view roots.
Rebuild discovery
php loom index:rebuild
php loom page:list
The page index records discovery and metadata; content parsing and caching are separate steps. Rebuild after adding, moving, or renaming pages. If the output looks stale, check caches and publication status.