Shorten the 1.3.0 notes and the export pages, and write down the rule - #106
Merged
Conversation
The release notes for 1.3.0 and 1.3.1 and the guide's export and frame paragraphs had grown into prose: mechanism, reasoning, and history that belong in docs/, in places read by people deciding whether to upgrade or looking up what a command does. They are cut to the length of their neighbours, in plain language, technically accurate. CONTRIBUTING gains "Writing for people": the site is two to four sentences per feature in the voice of the page; CHANGELOG entries are two to four lines saying what changed and what it is for; everything longer goes to docs/. The test is the neighbouring paragraphs. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Why
The 1.3.0 and 1.3.1 release notes and the guide's export and frame paragraphs had grown into prose: mechanism, reasoning, and history that belong in
docs/, placed where people decide whether to upgrade or look up a command. This was asked for once before.What changes
Once merged, the body of the v1.3.0 GitHub release should be replaced with the new 1.3.0 section; that is a one-line
gh release edit, and I can do it on request.🤖 Generated with Claude Code