Topic: content

Attach additional content directories at specific points in your site's URL tree using filesystem mounts.

Choose between two content models -- media-rich pages with folders or lightweight documentation with plain files -- and mix them freely in the same site.

Define content schemas with typed fields, validation rules, and defaults using YAML model files.

A markdown file is the page. No wrapper folder, no required frontmatter -- titles come from headings. Best for documentation, wikis, and serving an existing repository as-is.

A directory is the page. An index file carries the content, and everything beside it -- images, modules, child pages -- belongs to that page. Best for media-rich sites and composable landing pages.

Folder pages and file pages coexist in the same content tree. Use folders where assets matter and files where they do not -- the storage model is invisible downstream.

Serve the same site in several languages using filename suffixes -- the default language keeps its plain URLs, translations are served under language prefixes, and templates get a ready-made translation list for building a language switcher.

How a page's location and frontmatter bind it to a document model, and which frontmatter fields a model may govern.

Point Accent at any folder of markdown -- a project's docs, a notes directory, a repository root -- and it serves immediately, with no restructuring and no frontmatter.

Attach additional content directories at specific points in your site's URL tree using filesystem mounts.

Choose between two content models -- media-rich pages with folders or lightweight documentation with plain files -- and mix them freely in the same site.

Define content schemas with typed fields, validation rules, and defaults using YAML model files.

A markdown file is the page. No wrapper folder, no required frontmatter -- titles come from headings. Best for documentation, wikis, and serving an existing repository as-is.

A directory is the page. An index file carries the content, and everything beside it -- images, modules, child pages -- belongs to that page. Best for media-rich sites and composable landing pages.

Folder pages and file pages coexist in the same content tree. Use folders where assets matter and files where they do not -- the storage model is invisible downstream.

Serve the same site in several languages using filename suffixes -- the default language keeps its plain URLs, translations are served under language prefixes, and templates get a ready-made translation list for building a language switcher.

How a page's location and frontmatter bind it to a document model, and which frontmatter fields a model may govern.

Point Accent at any folder of markdown -- a project's docs, a notes directory, a repository root -- and it serves immediately, with no restructuring and no frontmatter.