Repository paths and output reference

When content publishes, Acrosite writes it into a fixed folder structure in your repository. This reference collects those paths in one place so you can set up your site's build to read from the right locations. For the detail and reasoning behind each path, see Acrosite-managed content paths.

Content paths

Each content type publishes to its own folder, with one Markdown file per content item named after that item's slug. The folders are created and managed by Acrosite:

acrosite/content/posts/<slug>.md       # Posts
acrosite/content/pages/<slug>.md       # Pages
acrosite/content/<type-key>/<slug>.md  # 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

Media is committed under public/images, with a folder per content type:

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.

What is in the file

Each published file is Markdown with frontmatter — title, slug, status, excerpt, an seo block, and a fields block for Custom Field values — followed by the body. See Generated Markdown and frontmatter.

Next steps

• Acrosite-managed content paths
• Generated Markdown and frontmatter
• Where media lands in your repository