Scheduled publishing workflow: from approval to GitHub commit
Scheduling Git-backed content shouldn't mean cron scripts or early commits. Acrosite keeps approved drafts private until the scheduled time, then validates the content, commits Markdown/MDX to GitHub, and triggers your configured deployment.
May rely on reminders, cron scripts, or early commits that the website has to filter.
May fit teams that want approved content to publish automatically at a scheduled time.
The right choice depends on whether you want manual timing or a built-in scheduled publishing workflow.
Manual publishing and Acrosite, compared
Approaches differ by team and setup — verify current specifics against each tool's documentation.
This is a high-level workflow comparison. The right fit depends on your website setup, team workflow, and publishing requirements.
What changes in the workflow?
- 01Someone remembers when content should go live.
- 02Content is committed by hand or via a script at that time.
- 03Early commits may need to be filtered by the website.
- 01The team creates Posts, Pages, and Custom Content Types.
- 02Writers and editors work without GitHub access.
- 03Client Reviewers can review their assigned content.
- 04Approved content can be scheduled.
- 05Acrosite commits to GitHub and records Publish Logs.
When should you choose which?
Publishing operations, built in
Review workflow
Move content through review and approval before publishing.
Scheduled publishing
Schedule approved content with date, time, and timezone.
GitHub publishing
Acrosite commits content to your connected repository.
Publish Logs
See trigger results and recovery context for each publish.
Client Reviewers
Clients review assigned content without GitHub access.
Posts, Pages & Custom Content Types
Model the content you publish across projects.
Custom Fields
Add the fields each content type needs.
Team Members
Give your team publishing roles without repository access.
Common questions
You schedule approved content for a future date, time, and timezone. Acrosite keeps it private until then, then commits it to GitHub.
No. Scheduled content is not committed early; it is committed at the scheduled publish time.
Publishing attempts are recorded in Publish Logs, failures are visible, and safe retry paths are available where possible.
For a single timed publish without an ongoing schedule, a manual commit may be enough.
Try a simpler Git-backed publishing workflow.
Registration is coming soon. Contact us to talk through your publishing workflow, or read the docs to see how Acrosite works.