Content goes in.Commits come out.
Acrosite is a Git-backed content publishing platform. Writers, editors and clients create, review, approve and schedule content in a structured workspace — and Acrosite generates the required files, commits them to the connected GitHub repository and triggers the configured deployment.
Developers keep full control of the repository and the website's architecture. Contributors never need direct GitHub or source-code access.
acrosite.com opens in a new tab as an external website.
The publishing pipeline
Six stages, one controlled path.
Walk a content object from unfinished draft to published change. Every stage shows who is involved, what happens and what stays controlled.
Draft
01 / 06
WHO IS INVOLVED
Writers and editors, in a structured editor.
WHAT HAPPENS
Content is created with the fields, media and SEO information the website expects — no repository access needed.
WHAT STAYS CONTROLLED
The website’s architecture stays untouched; drafts live only in the workspace.
WHAT IT PRODUCES
A draft content object, versioned from its first save.
Who. Writers and editors, in a structured editor.
What. Content is created with the fields, media and SEO information the website expects — no repository access needed.
Controlled. The website’s architecture stays untouched; drafts live only in the workspace.
Produces. A draft content object, versioned from its first save.
Who. Editors, reviewers and clients.
What. Feedback and revisions happen against the draft itself, in one place instead of email threads.
Controlled. Nothing reaches the repository while content is under review.
Produces. A reviewed draft with resolved feedback.
Who. Approvers with the right role.
What. The content is signed off — published immediately or scheduled for the agreed moment.
Controlled. Role-based participation decides who may approve and publish, per workspace.
Produces. An approved object with a publish decision attached.
Who. Acrosite, automatically.
What. The platform generates the exact content files the website’s architecture expects.
Controlled. Developers define the structure and location the files must follow.
Produces. Ready-to-commit content files.
Who. Acrosite, acting for the team.
What. The generated files are committed to the connected GitHub repository.
Controlled. The repository, its branches and its history remain under developer control.
Produces. A clean, attributable commit.
Who. The team’s configured workflow.
What. The commit triggers the deployment workflow the developers set up.
Controlled. Build and hosting stay the team’s own — Acrosite does not host the website.
Produces. The published change, live on the site.
Who works in Acrosite
Everyone who touches content — each with the right role.
Role-based participation and separated workspaces keep multi-website, multi-client and multi-project work organised: agencies manage many sites, clients see their own, and developers decide what the platform may touch.
Agencies
Many clients, one workspace each
Website owners
Publishing without a developer queue
Content teams
Drafts, reviews and schedules in one place
Writers & editors
A structured editor, not a code editor
SEO professionals
Metadata and structure, per page
Clients
Review and approve, nothing more
Developers
Repository and architecture, untouched
Reviewers
Approval steps that actually gate
Around the workflow
What the workspace keeps track of.
- 01
Version history
Every change to every content object, traceable
- 02
Media
Images and files, organised alongside the content
- 03
SEO information
Titles, descriptions and structure captured per entry
- 04
Structured content
Fields that match the website's architecture — defined by developers
- 05
Scheduling
Approved content, published at the agreed moment
- 06
Workspaces
Websites, clients and projects kept cleanly apart
The boundary
What Acrosite does not try to be.
Not a replacement for GitHub. The repository stays the source of truth; Acrosite writes to it through a controlled workflow.
Not a replacement for developers. Architecture, components and deployment remain engineering decisions.
Not a website host. The site builds and deploys wherever the team configured it — Acrosite triggers the workflow, nothing more.
It is the layer in between: a structured, reviewable, role-aware path from content to commit.
Delivery is GitHub-based. Questions about a specific setup? Contact about Acrosite.
Give your writers a pathto production.
Acrosite is a Zealsync product. Reading on: the full portfolio or insights on publishing operations.