On this page
Getting Started

How Acrosite works

A clear end-to-end picture: you write in Acrosite, Acrosite commits Markdown to your GitHub repository, and then triggers your host to redeploy.

OverviewFor Anyone evaluating AcrositeUpdated November 12, 2026

Acrosite connects three things: a dashboard where your team writes, your website's GitHub repository where content is stored as Markdown, and a deployment method that gets your host to rebuild. This page explains how they fit together.

The three parts

  • The Acrosite dashboard — where writers, editors, and clients create and review content in a clean editor. No one needs GitHub access to use it.
  • Your GitHub repository — where Acrosite commits published content as Markdown files, in the folders set for each content type (by default under acrosite/content), which your site reads from.
  • Your deployment method — most hosts rebuild from each commit on their own (Git-connected). Otherwise Acrosite can call a Vercel, Netlify or Cloudflare Pages deploy hook after the commit, or you can deploy manually.

A publish, step by step

When content is ready, here is what happens:

  1. An editor writes a Post or Page in Acrosite.
  2. If your team uses review, a reviewer — a teammate or a Client Reviewer — approves it. Review is optional.
  3. The content is published now or on a schedule.
  4. Acrosite commits the Markdown (and any images) to your repository on the branch you chose.
  5. Your host rebuilds the site: from the commit on its own (Git-connected), when Acrosite calls your deploy hook, or when you deploy it yourself (Manual).
  6. The result is recorded in Publish Logs and Deployment Logs.
Important
Acrosite triggers your deployment and records the response; a trigger does not mean the build finished. Owners and Admins see the build status your host reports to GitHub for each publish — see Build status. If your host reports nothing, confirm the finished build in your provider's dashboard.

What Acrosite is not

Acrosite is not a website host and not a visual page builder. Your site keeps building and deploying exactly as it does today — Acrosite only changes how content gets into the repository. Your content stays in your repo, in your control.

Next steps

Frequently asked questions

No. Writers, editors, and Client Reviewers work entirely in the Acrosite dashboard. Acrosite commits the content for them, so no one outside your developers needs repository access.
No. Acrosite stores content in your GitHub repository and triggers your existing host to rebuild. Your site is hosted wherever it is hosted today.
Content is committed as Markdown or MDX with frontmatter, in the folder set for each content type (by default under acrosite/content), so your site framework can read it during the build.
Acrosite confirms the commit and, for a deploy hook, that the trigger was sent and accepted. Owners and Admins also see the build status your host reports to GitHub for the commit; it says Deployed only when Acrosite recognizes your hosting provider's own status. If there is none, check your host's dashboard to confirm the live site updated.