You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add GitHub Actions CI for Markdown Linting and Manifest Integrity #198
This issue proposes introducing an automated GitHub Actions CI workflow to validate markdown files and verify the integrity of bin/handbook-manifest.json on every pull request and push to trunk.
Currently, the repository has no automated CI checks for documentation quality or synchronization readiness:
Manifest Discrepancies:bin/handbook-manifest.json defines the sidebar hierarchy and URL routing on Make WordPress. When new guides are added, renamed, or moved, it is easy for contributors to forget to register them in the manifest (or leave stale entries behind).
Markdown Inconsistencies: Fenced code blocks without language specifiers, malformed headings, broken relative links, and invalid HTML can slip through manual reviews.
Automating these checks in CI will give contributors and reviewers fast, automated feedback and prevent broken handbook synchronizations.
Add a configuration file for markdownlint-cli tailored to Make WordPress handbook conventions (e.g. allowing certain handbook callout HTML tags like <div class="callout..."> while enforcing proper heading hierarchy and fenced code block languages).
Activity