Keep the considered page focused on omissions readers need explained - #234
Merged
Merged
Conversation
Deploying specification-website with
|
| Latest commit: |
8e429fd
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d428e182.specification-website.pages.dev |
| Branch Preview URL: | https://codex-narrow-considered-regi.specification-website.pages.dev |
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.
The considered page had grown into a catalogue of routine exclusions, making it harder to see which omissions need an explanation. Reduce it from 19 entries to the seven that readers could reasonably expect this specification to cover, and explain that narrower purpose on the page.
Apply the same rule in the contribution guidance and daily standards scan: a public entry needs a clear reader benefit and a connection to existing guidance or a direct website outcome. Keep routine exclusions in internal notes, while preserving maintainer decisions about topics with thin adoption.
Validation: lint, formatting, skill checks, Astro check and production build pass. The built page contains exactly the seven retained entries, and no references to removed entry anchors remain.