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.
Acrosite connects three things: a dashboard where your team writes, your website's GitHub repository where content is stored as Markdown, and a deployment trigger that tells 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 approved content as Markdown files, in a fixed folder structure your site reads from.
- Your deployment trigger — an optional deploy hook Acrosite calls after a commit so your host rebuilds the site. Acrosite supports Vercel deploy hook triggers or Manual / No Automatic Deployment, with more providers Coming Soon.
A publish, step by step
When content is ready, here is what happens:
- An editor writes a Post or Page in Acrosite and submits it for review.
- A reviewer — a teammate or a Client Reviewer — approves it.
- The content is published now or on a schedule.
- Acrosite commits the Markdown (and any images) to your repository on the branch you chose.
- Acrosite sends your deployment trigger so your host rebuilds the site.
- The result is recorded in Publish Logs and Deployment Logs.
Important
Acrosite triggers your deployment and records the response, but it does not track your host's build to completion. 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
- Learn the vocabulary in Core concepts.
- Follow the Getting started tutorial.
- Connect a project to GitHub with Connect GitHub.
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 with frontmatter in a fixed folder structure in your repository, so your site framework can read it during the build.
Acrosite confirms the commit and that the deployment trigger was sent and accepted. It does not track the build to completion, so check your host's dashboard to confirm the live site updated.