docs: improve README onboarding and documentation generation#1
Merged
Conversation
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
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
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
API.md, while directing users to pkg.go.dev for the complete exported API.200/204examples and teachPrefor middleware that must affect route matching.Why
The README had grown to 1,708 lines, with most of the useful onboarding buried beneath a generated reference that did not include important exported types and configuration fields. New users could see several ways to register routes, but not why they would choose one or how the packages fit together.
Some examples were also actively misleading: status-code output did not match the code, and path- or method-changing middleware was shown in the wrong routing phase. The standalone example generator could not reproduce current GoDoc without truncating programs, which allowed checked-in examples and their source comments to drift apart.
This gives users a shorter path from installation to a working application, makes operational boundaries explicit, and restores documentation generation as a reproducible source-of-truth workflow without changing the public API or minimum Go version.