Skip to content

Add CI/CD pipeline for deploying governance docs#4

Merged
JohnRDOrazio merged 5 commits intomainfrom
feature/ci-deploy-pipeline
Apr 5, 2026
Merged

Add CI/CD pipeline for deploying governance docs#4
JohnRDOrazio merged 5 commits intomainfrom
feature/ci-deploy-pipeline

Conversation

@JohnRDOrazio
Copy link
Copy Markdown
Member

@JohnRDOrazio JohnRDOrazio commented Apr 5, 2026

Summary

  • Add GitHub Actions deploy workflow (deploy-docs.yml) triggered on v* tags and workflow_dispatch
  • Add markdown linting workflow (markdown-lint.yml) on push/PR
  • Add package.json with build scripts, linting, and dev dependencies
  • Add build tooling for standalone HTML (per-document, with cross-nav links) and a single combined PDF
  • Add TeX Gyre Schola fonts and Paged Media CSS for PDF output
  • Add .markdownlint.yml config and format all docs with prettier

Details

  • Documents are deployed as WordPress pages under section parents (ai-governance, project-governance, standards)
  • Only changed documents are converted and deployed (diff against previous tag)
  • Deployed pages are translated to it, es, fr, pt, de via cdcf/v1/translate
  • All standalone HTML files and the combined PDF are attached to GitHub releases
  • Follows the deployment pattern from foundation-bylaws, foundation-manifesto, and foundation-logo

Closes #5

Test plan

  • Verify npm run build:html produces individual HTML files in dist/ with working nav links
  • Verify npm run build:pdf produces a single combined PDF in dist/
  • Verify npm run lint:md runs markdownlint across all docs
  • Push a v* tag and confirm the deploy workflow runs successfully
  • Confirm WordPress pages are created/updated under correct parent pages

🤖 Generated with Claude Code

JohnRDOrazio and others added 2 commits April 5, 2026 15:15
Add GitHub Actions workflows and build tooling to deploy all governance
documents as WordPress pages, build standalone HTML with cross-navigation,
and produce a single combined PDF for releases.

Closes mj3b#2

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…nance/committees

Prefix standards docs with "standards-" in WordPress slugs to avoid
both committees.md files mapping to the same page slug.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@JohnRDOrazio JohnRDOrazio force-pushed the feature/ci-deploy-pipeline branch from bdd8dc3 to 76660e2 Compare April 5, 2026 13:16
JohnRDOrazio and others added 3 commits April 5, 2026 15:17
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Add .markdownlint.yml matching sibling repos (180-char line length,
  disable bare URL rule for reference sections, allow div elements)
- Add package-lock.json required by npm ci in CI
- Auto-format all markdown with prettier (prose-wrap at 180 chars)
- Remove broken TOC link in project-vetting-criteria.md

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
WP_REST_URL is configured as a repository variable, not a secret.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@JohnRDOrazio JohnRDOrazio merged commit 8868c5e into main Apr 5, 2026
1 check passed
@JohnRDOrazio JohnRDOrazio deleted the feature/ci-deploy-pipeline branch April 5, 2026 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add CI/CD pipeline for deploying governance docs to WordPress

1 participant