Publishing in BulkheadOS is designed as one connected workflow: write once, review the public impact, ship the page, and verify the surfaces readers and external tools will use.
Workflow At A Glance
| Step | HQ surface | What to check |
|---|---|---|
| 1. Draft | Library | Title, slug, body, summary, owner, and content type. |
| 2. Review | Governance | Domain language, tone, required terms, and whether Git owns the content area. |
| 3. Preview | Content editor | Rendered page, metadata, links, image alt text, and any read-only Git banner. |
| 4. Publish | Library or Git Sync | Status, branch or source commit, and the expected public URL. |
| 5. Verify | Discovery | HTML page, markdown alternate, structured data, sitemap, search, and machine-readable discovery files. |
| 6. Learn | Feedback and comments | Repeated questions, page feedback, public replies, and support friction. |
Before You Publish
- Confirm the page answers one clear reader job.
- Use the customer's words in headings and examples where possible.
- Check every internal link and any external link that affects trust.
- Add image alt text that explains the image, not just the file name.
- Make sure the summary is suitable for search results and social previews.
Git-Managed Content
If the content area is connected to Git, HQ shows it as read-only. Make the content change in the repository, then let Git Sync update the page. This keeps authors from accidentally maintaining one version in Git and another version in HQ.
Release habit: Put the public page URL in the pull request or commit note. Reviewers can compare the intended customer page with the source change before it ships.
After You Publish
- Open the live page and confirm it returns
200. - Open the markdown alternate at the same path with
.md. - Open the structured data link shown in the page header.
- Search for a phrase from the page using the site search.
- Check the relevant discovery file if the page changes public action guidance.
- Watch feedback and comments for follow-up questions.
What Good Looks Like
A good release leaves no split story. The page, metadata, search result, markdown alternate, structured data, and machine-readable discovery files all point to the same reviewed explanation.