On this page
Reference

Repository paths and output reference

A single table of where Acrosite writes in your repository — Posts, Pages, Custom Content Types, and media — and how files are named and referenced.

ReferenceFor DevelopersUpdated November 12, 2026

When content publishes, Acrosite writes it into folders in your repository. This reference collects the default paths in one place so you can set up your site's build to read from the right locations, and shows how to change them. For the detail, see Acrosite-managed content paths.

Content paths

Each content type publishes to its own folder, with one file per content item named after that item's slug. MDX is the default file type:

Paths
acrosite/content/posts/<slug>.mdx       # Posts
acrosite/content/pages/<slug>.mdx       # Pages
acrosite/content/<type-key>/<slug>.mdx  # Custom Content Type items

The type-key is generated from a Custom Content Type's plural name and is protected after creation. See Slugs and output filenames.

Media paths

By default media is committed under public/images, with a folder per content type:

Paths
public/images/posts         # Post images
public/images/pages         # Page images
public/images/<type-key>    # images for a Custom Content Type

A file committed at public/images/posts/name.webp is referenced in your Markdown as /images/posts/name.webp (the public prefix is dropped, since most frameworks serve public at the web root). See Where media lands in your repository.

Change the paths

Each content type's Repository Output settings change its content folder, file type (MDX or Markdown), media folder and media URL. Files already published stay where they are until an item is published again; Acrosite then writes it to the new folder and removes the old file if it is unchanged. Uploads after the change use the new media folder. See Acrosite-managed content paths.

What is in the file

Each published file is Markdown with frontmatter — title, slug, excerpt, status, the publishing dates, the content type, the SEO keys and each Custom Field under its own key — followed by the body. See Generated Markdown and frontmatter.

Developer note
Set each content type's Repository Output to the folders your site already reads, or keep the defaults and map them during your build.

Next steps