docs(safe-harbor): normalize structure and wording - #573
Open
mattaereal wants to merge 5 commits into
Open
Conversation
Add Key Takeaways, page map, related frameworks, and contributor roles. Preserve legal/process content without substantive rewrite (steward-owned).
Deploying frameworks with
|
| Latest commit: |
93e7c92
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://311a7d85.frameworks-573.pages.dev |
| Branch Preview URL: | https://docs-normalize-safe-harbor.frameworks-573.pages.dev |
Rewrite non-stub frontmatter descriptions into the acceptable length band (preferred 140–160). Stub pages exempt. No body or credit changes.
Child pages missing a canonical further/related H2 failed the updated #561 validator. Add a minimal Further Reading block linking the framework overview.
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
2 participants
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.
Scope
Normalize Safe Harbor chrome (
docs/pages/safe-harbor/) only.Why
Missing Key Takeaways and overview page map/related routing; incomplete contributor role slots.
Content model applied
Initiative/framework hybrid; no legal text redesign. Structural chrome + navigation only.
Substantive security/legal changes
None. Existing claims, FAQ, adoption steps, whitehat procedures unchanged aside from KT + navigation sections.
Intentionally unchanged
Validation
Dependencies
#561 by reference.
Expert review required
Legal / Safe Harbor stewards for any future wording on enforceability, bounties, or adoption claims.