Publishing workflowFrom draft to GitHub commit, step by step

From draft to GitHub commit
in one clean workflow.

Connect your Git-backed website, create content in Acrosite, route it through review, schedule it, and let Acrosite commit the final Markdown/MDX file to GitHub and trigger the configured deployment trigger profile.

GitHub AppMarkdown / MDXDeployment triggersClient ReviewersPublish Logs

THE WORKFLOW

Six steps from content idea to GitHub commit.

Acrosite keeps content work simple for non-technical users while preserving GitHub as the final source of truth for published content.

Connect GitHub
Install the Acrosite GitHub App and select the repository your project should publish to.
Configure the project
Choose the branch, content paths, media paths, file format, and deployment trigger profile.
Create content
Create Posts, Pages, and Custom Content Types with SEO fields, Custom Fields, and media references.
Review and approve
Team Members and Client Reviewers can comment, approve, or request changes without GitHub access.
Schedule or publish
Publish immediately or schedule approved content for a future date, time, and timezone.
Commit and trigger
Acrosite commits Markdown/MDX to GitHub and triggers the configured deployment trigger profile.

STEP 1

Connect your Git-backed website.

Acrosite connects to your website repository through a GitHub App, so you do not need to share personal access tokens or give clients GitHub access.

Install the Acrosite GitHub App
Select the allowed repository
Choose the project repository
Keep access scoped and revocable

STEP 2

Tell Acrosite where content should go.

Choose the branch, content folders, media output paths, Markdown/MDX format, and deployment trigger profile for each project.

Branch selection
Posts path, Pages path, Custom Content Types path
Media path
Deployment trigger profile (masked, server-side)

STEP 3

Create Posts, Pages, and Custom Content Types.

Your team creates content in Acrosite using structured fields, SEO fields, slugs, media references, and project-specific Custom Fields.

Posts for blogs, guides, updates, and articles
Pages for landing pages, service pages, and location pages
Custom Content Types for case studies, FAQs, authors, services, and more
SEO fields built into the publishing workflow

STEP 4

Route reviews to the right people.

Send content to Team Members or Client Reviewers for comments, approval, or requested changes. Client Reviewers only see assigned review work and do not need GitHub access.

Internal team review
Client approval and request-changes flow
Comment threads
Assigned-content-only visibility

STEP 5

Schedule content without committing it early.

Approved content can be published immediately or scheduled for a future time. Scheduled drafts stay in Acrosite until publish time, so websites do not need to filter future-dated content.

Publish Now or schedule for later
Date, time, and timezone-aware scheduling
Content Calendar visibility
Scheduled drafts remain private until publish time

STEP 6

Acrosite commits to GitHub and triggers the configured deployment trigger profile.

At publish time, Acrosite validates the content, generates Markdown/MDX with frontmatter, commits the file to GitHub, saves the commit SHA, and triggers the project's configured deployment trigger profile.

Pre-publish validation and Markdown/MDX generation
GitHub commit + commit SHA saved
Configured deployment trigger profile
Deployment trigger result recorded in Publish Logs

WHO DOES WHAT

Everyone gets the right workflow — without exposing GitHub.

Acrosite separates content work, technical setup, client review, and publishing authority.

Agency owners

Oversee workspaces, projects, billing, clients, team access, and publishing operations.

Developers

Connect GitHub, configure branches and paths, set up deployment triggers, and keep technical settings safe.

Editors and content teams

Create, edit, review, approve, schedule, and manage content from one dashboard.

Client Reviewers

Review assigned content, leave comments, approve, or request changes without seeing GitHub, billing, or internal settings.

PERMISSIONS4 roles

GitHub settingsDeveloperOwner

BillingOwner

Content reviewTeam MembersClient Reviewers

PublishAuthorized internal roles

PUBLISHING ENGINE

What happens at publish time?

When a scheduled publish time arrives, Acrosite runs a protected publishing job. It checks workspace state, validates content, generates files, commits to GitHub, triggers the configured deployment trigger profile, and records the result.

PUBLISH JOB · scheduled · 09:00 IST● COMPLETE

01Re-check workspace and subscription statusWorkspace ok · plan active
02Re-check user and project permissionsRoles validated
03Validate required content fieldsAll required fields present
04Confirm media references are ready12 / 12 media items found
05Generate Markdown/MDX and frontmatterposts/local-seo-guide.mdx
06Commit content and media to GitHubbranch · main
07Save commit SHA0fa3b9c
08Trigger configured deployment trigger profileDeployment triggered
09Record Publish Loglog id · pl_12d8a
10Notify relevant users if needed1 author · 1 reviewer

RECOVERY BUILT IN

Publishing should be visible, logged, and recoverable.

Acrosite is designed so publishing failures do not disappear silently. Publish Logs show what happened, where it failed, and what can be retried.

Publish Logs

Every publish attempt records validation, GitHub commit, deployment trigger status, timestamps, and safe failure messages.

Safe retry paths

If a publish job fails, authorized users can retry where safe. If the GitHub commit succeeded but the deployment trigger failed, Acrosite can retry the deployment trigger without recommitting content where possible.

Clear failure states

Content can move through Draft, In Review, Approved, Scheduled, Publishing, Published, Failed, and Archived states.

PUBLISH RESULTFailed

FAQ: Pricing Questions

✓ Commit saved 0fa3b…

! Deployment trigger rejected request

reason: 502 from provider

CLEAR BOUNDARIES

What Acrosite is — and what it is not.

Acrosite is intentionally focused on Git-backed content publishing. That keeps the product simple, reliable, and easier for agencies to adopt.

Acrosite is

A Git-backed content publishing platform.
A dashboard for Posts, Pages, and Custom Content Types.
A review, scheduling, and publishing workflow layer.
A way to publish to GitHub without giving clients GitHub access.
A provider-neutral deployment trigger layer for connected projects.
A workspace, client, and project operating layer for agencies and developers.

Acrosite is not

A visual website builder.
A full enterprise CMS.
A replacement for your website frontend.
A tool that gives clients repository access.
A generic database modeling platform.
A promise of full deployment lifecycle tracking.

BEFORE YOUR FIRST PUBLISH

What you need to connect your first project.

Acrosite works best when your Git-backed website has clear content paths and a deployment trigger ready.

GitHub repository

Your website source code should be in a GitHub repository.

Content folders

Decide where Posts, Pages, Custom Content Types, and media should be written.

Markdown or MDX structure

Confirm how your website reads frontmatter and content files.

Deployment trigger profile

Choose Manual / No Automatic Deployment or configure automatic Vercel deploy hook triggers, with more providers Coming Soon.

Review roles

Decide who can create, approve, review, schedule, and publish content.

WORKFLOW FAQ

Questions about the workflow.

Need something more specific? The docs go deeper on setup, repository configuration, scheduling, and publish recovery.

Open documentation

Do clients need GitHub access?

No. Client Reviewers can review assigned content inside Acrosite without seeing GitHub, billing, deployment triggers, team settings, or unrelated projects.

Does Acrosite commit scheduled content early?

No. Scheduled content stays in Acrosite until publish time. At the scheduled time, Acrosite validates the content and commits it to GitHub.

Does Acrosite deploy my website?

Acrosite commits content to GitHub and triggers the configured deployment trigger profile. Acrosite supports Manual / No Automatic Deployment and automatic Vercel deploy hook triggers. Netlify, Cloudflare Pages, GitHub Actions, Custom Webhook, Render, DigitalOcean App Platform, AWS Amplify, GitHub Pages, and Firebase Hosting appear as Coming Soon and cannot be configured yet. The UI says “Deployment triggered” because Acrosite records the trigger request and the provider's response, not build completion.

What file format does Acrosite publish?

Acrosite is designed around Markdown/MDX files with frontmatter, so Git-backed websites can consume published content from the repository.

What content types can I publish?

You can manage Posts, Pages, and Custom Content Types. Custom Content Types can support structures like Case Studies, FAQs, Services, Locations, Authors, Testimonials, and more.

What happens if publishing fails?

Acrosite records the failure in Publish Logs, shows a safe failure reason, and supports retry paths where possible.

Can developers still control the technical setup?

Yes. Developers can configure repository, branch, content paths, media paths, and deployment trigger profiles while content teams use the publishing workflow.

START HERE

Ready to make Git-backed publishing easier?

Connect your Git-backed website, create content with your team, route it through review, schedule it, and let Acrosite commit the final files to GitHub.