Clients should not need repository access.
Client stakeholders can review content without seeing branches, commits, repository files, or deployment settings.
Acrosite connects through a GitHub App, writes Markdown/MDX with frontmatter to your repository, records commit details in Publish Logs, and triggers the configured deployment trigger profile after publishing.
A repository is built for code, branches, and commits — not as an everyday editing surface for clients, writers, and reviewers. GitHub Publishing keeps the repo central while keeping content work out of it.
Client stakeholders can review content without seeing branches, commits, repository files, or deployment settings.
Content creators need a clean editing workflow, not direct access to Markdown files inside GitHub.
Simple content updates should not become repeated commit and deployment tasks.
Published content should remain traceable through commits, file paths, and commit SHA records.
Acrosite writes content to the paths your website expects instead of forcing a new frontend architecture.
Acrosite records deployment trigger results without pretending to track the full provider lifecycle.
Acrosite uses a GitHub App connection so repository access can be scoped, managed, and revoked without sharing personal access tokens.
Access is scoped and revocable. Connection is managed through GitHub App installation settings — not shared tokens.
Each project can define where Posts, Pages, Custom Content Types, and media should be written in the connected repository.
At publish time, Acrosite turns an approved item into a committed file in your repository — then hands off to your deployment trigger profile.
Acrosite separates technical setup from everyday content work, so each role gets the access it needs.
Connects GitHub, selects repository and branch, configures content paths, media paths, and deployment trigger profiles.
Reviews, approves, schedules, publishes, and monitors Publish Logs.
Creates and edits Posts, Pages, and Custom Content Types without repository access.
Reviews assigned content, comments, approves, or requests changes without seeing GitHub.
Publish Logs help teams understand whether content was validated, committed to GitHub, and whether the deployment trigger was accepted.
Store file path, branch, commit status, and commit SHA.
If commit or trigger fails, the failure is logged with a safe reason.
Authorized users can retry where safe, including deployment-trigger-only retries when applicable.
After the GitHub commit succeeds, your site deploys the way the project is set up: your host builds from the commit, Acrosite calls a deploy hook and records the result, or you deploy by hand.
Your host is connected to the repository and builds from each commit Acrosite makes. No hook is needed.
Acrosite calls your Vercel deploy hook after the commit and records the response.
Acrosite calls your Netlify build hook after the commit and records the response.
Acrosite calls your Cloudflare Pages deploy hook after the commit and records the response.
No automatic deployment. Acrosite commits the content and you deploy from your host on your own schedule.
Any other host that builds from your repository works through Git-connected. Otherwise, deploy it yourself with Manual.
A focused publishing layer with deliberate edges — here is what it does, and what it does not try to be.
A short, technical setup — usually done once by a developer — before content teams start publishing.
Your website source code and content output should live in a GitHub repository.
Install the Acrosite GitHub App and allow access to the selected repository.
Choose the branch Acrosite should publish to.
Define paths for Posts, Pages, Custom Content Types, and media.
Confirm how your website reads frontmatter and content files.
Choose Manual / No Automatic Deployment or configure a supported automatic trigger profile.
Access, tokens, file format, scheduling, deployment triggers, and recovery — the specifics teams ask before connecting a repository.
Open documentationCreate your workspace, connect a Git-backed project, map content paths, and test GitHub publishing with a 14-day free trial.