Acrosite-managed content paths
Acrosite writes content into a fixed folder structure in your repository — Posts, Pages, Custom Content Types, and media. Here is where each file lands.
When Acrosite publishes, it writes content into a fixed folder structure in your repository. These paths are managed by Acrosite and are the same for this release. This page shows where each kind of file lands so your site can read it.
Who this is for
Developers connecting a site to Acrosite, and anyone curious where published files go.
The managed paths
Acrosite saves generated content inside a dedicated acrosite/content folder so developers can identify Acrosite-managed files, and writes media under public/images to keep public image URLs clean:
acrosite/content # content root
acrosite/content/posts # Posts
acrosite/content/pages # Pages
acrosite/content/<type-key> # each Custom Content Type
public/images # media
public/images/<type-key> # media for a Custom Content TypeEach Post, Page, or Custom Content Type item is committed as a Markdown file with frontmatter in its folder. Images the content uses are committed under the media path.
Why the paths are fixed
A predictable structure keeps your repository tidy and makes Acrosite-managed files easy to recognise. It also means your site's templates can rely on stable locations for Posts, Pages, and each Custom Content Type.