You own your content and repository
Acrosite is Git-backed: it commits your content as Markdown to your own GitHub repository, so your content and its history live with you, not locked inside Acrosite.
Acrosite is Git-backed: it commits your content as Markdown to your own GitHub repository. That means your content — and its full history — lives with you, in a repository you control, not locked inside Acrosite. This page explains what that gives you.
Who this is for
Workspace Owners and anyone evaluating Acrosite who wants to know where their content lives.
Your content lives in your repository
When you publish, Acrosite commits the content item (and the images it uses) into your GitHub repository as Markdown with frontmatter, in a managed folder structure. Because it is in your repository:
- You have the files, the history, and the commits.
- Your site builds from your repository, the same as any other Git-based site.
- You are not dependent on Acrosite to serve your published content.
See Acrosite-managed content paths for exactly where files land.
Acrosite is the authoring layer
Acrosite gives your team a clean place to write, review, schedule, and publish — and it keeps a workspace-scoped record of drafts, structure, review history, and logs to make that work. The published source of truth is your repository. See What Acrosite stores about your content.
You stay in control
Because access runs through a scoped GitHub App, you choose which repositories Acrosite can write to, and you can manage or revoke that access from your GitHub installation settings at any time.