Publish Readiness Checklist
Confirm required fields, SEO fields, media references, review status, GitHub setup, and the deployment trigger profile before publishing.
Back to Templates
Publishing Workflows
Publish Logs Troubleshooting Checklist
A troubleshooting checklist for reading failure reasons, Commit SHA, file path, and trigger result.
1
When to use this template
Use this checklist when a publish attempt fails — work through Publish Logs to read the safe failure reason, Commit SHA, generated file path, and deployment trigger result.
Publish Logs record every attempt, so a structured pass helps you find the safe retry path without exposing raw provider payloads.
2
Suggested fields
A starting set of fields for this structure. Adapt the labels, keys, and which fields are required to match your project.
Field labelField keyTypeStatus
Item TitletitletextRequired
Failure ReasonfailureReasontextRequired
Commit SHAcommitShatextOptional
Generated File PathfilePathtextOptional
Trigger ResulttriggerResultstatusOptional
SEO TitleseoTitletextSEO
Meta DescriptionmetaDescriptiontextareaSEO
3
Required fields
The minimum fields every item should have before it can move to review.
Field labelField keyTypeStatus
Item TitletitletextRequired
Failure ReasonfailureReasontextRequired
4
Optional fields
Useful additions you can include per item, or leave out when they don't apply.
Field labelField keyTypeStatus
Commit SHAcommitShatextOptional
Generated File PathfilePathtextOptional
Trigger ResulttriggerResultstatusOptional
5
SEO fields
Search metadata for the item. Keep titles and descriptions unique per item.
Field labelField keyTypeStatus
SEO TitleseoTitletextSEO
Meta DescriptionmetaDescriptiontextareaSEO
6
Example content item
titleLocal SEO Guide
failureReasonMedia reference not found
commitShaa1b2c3d
filePathcontent/posts/seo-guide.mdx
triggerResultNot triggered
7
Markdown / MDX frontmatter example
How the structure looks as frontmatter in a Git-backed content file. Field keys map directly to your content type.
---
title: "Local SEO Guide"
status: "failed"
failureReason: "Media reference not found"
---
# Resolution steps
Content body…8
Review & publishing checklist
Confirm these before publishing the item through GitHub. The trigger result is recorded in Publish Logs.
All required fields completedFill every field marked Required before moving to review.
Featured Image reference resolvesConfirm the media path exists in your repo.
SEO Title and Meta Description setWithin recommended length, unique per item.
Sent to Client Reviewers for approvalAdd review context so reviewers know what changed.
Scheduled or ready to publishConfirm date, time, and timezone if scheduling.
Deployment trigger profile configuredTrigger result is recorded in Publish Logs after publishing.
Turn templates into a publishing workflow.
Use Acrosite to create the structure, review content, schedule publishing, and keep output in GitHub.