Ban em dashes in copy: policy, CI check, full site pass - #12
Merged
Conversation
Reverses the "house voice uses em dashes" rule. CLAUDE.md now bans em dashes in copy and anything that ships; validate_site.py fails CI on a literal em dash or its HTML entities in any text file of the build output. All existing em dashes across content/*.yaml, templates, and shipped assets are removed by restructuring each sentence (pipes in titles, commas/colons/periods in prose). Internal docs keep theirs; they do not ship. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for qfearless ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Reverses the repo's "house voice uses em dashes" convention:
tools/validate_site.py(already run by CI on the builtdist/) now walks every shipped text file (HTML, CSS, JS, XML, JSON, MD, SVG, TXT, webmanifest) and fails on a literal em dash or the—/—/—entities, reporting file:line.content/*.yaml, theog/twitterimage alts inBaseLayout.astro, the contact form subject + shipped comment, and user-facing strings/comments inmain.js,gate.js,style.css, the img README, and the Keystatic admin strings. Page titles now use pipes ("Work | Quentin Fears | ..."); the footer tagline is back to the brief's comma form ("Don't just wear clothes, wear confidence").Internal docs (README, PROPOSAL, ASSETS, docs/) keep their em dashes; they do not ship and the check reads the build output only.
Validation
npm run buildsucceeds;validate_site.py distandseo_check.py distpass clean (6 pages, 0 warnings).dist/index.htmlfails with exit 1 and the right file:line; clean build passes.🤖 Generated with Claude Code