Skip to content

refactor(content): one instruction per rule, the slash rules together - #2112

Open
braboj wants to merge 1 commit into
mainfrom
refactor/content-score
Open

braboj wants to merge 1 commit into
mainfrom
refactor/content-score

Conversation

@braboj

@braboj braboj commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

Raises frontend/content from 90.7 to 99.1: SEO statements become instructions, and compound rules split.

Section (ID kept) Change
Lead-in Two sentences, the second about who extends it, → one
Content structure Lead paragraph → two rules; the table stays
SEO "X required" statements → "Add X", "Give every page Y"
SEO JSON-LD "appropriate schema type" hedge → "the type that matches the page" (SHOULD kept)
SEO og:image/twitter:image and the H1 rule each split in two (MUST, SHOULD, SHOULD kept)
SEO → Trailing slash The pick-a-convention MUST moves beside the hosting check

Checks

  • Smoke 35/35; conformance 12 passed, 0 failed, 1 not applicable; readings read
  • Fork sync, redundancy audit, score ratchet, markdownlint, pre-commit hooks

No CHANGELOG entry: the rules are unchanged in meaning.

🤖 Generated with Claude Code

SEO rules written as statements become instructions; the og:image and
H1 rules split in two. The trailing-slash convention joins its own
section. Every MUST, SHOULD and MAY keeps its strength.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant