docs(blog): accuracy pass and backfill posts through 0.1.0 beta#57
Open
phil-scott-78 wants to merge 1 commit into
Open
docs(blog): accuracy pass and backfill posts through 0.1.0 beta#57phil-scott-78 wants to merge 1 commit into
phil-scott-78 wants to merge 1 commit into
Conversation
….0 beta The launch posts were written in one batch and drifted as the code moved. Corrections against current source: - introducing-pennington: AddDocSite takes a Func<DocSiteOptions> - structured-data: core ships JsonLdArticle/Person/WebSite/BreadcrumbList - llms-txt: the front-door header file is llms-header.txt, not llms.txt - catch-broken-links: four auditors shipped, not two; drop the single-source claim - api-reference: de-dup the how-to link; robots-only is a C# skeleton, not HTML - build-report, pennington-on-nuget, data-files, dotnet-new-templates, documentation-in-every-language: smaller fixes New posts continuing the timeline (2026-05-19 to 2026-06-22): - Content tabs, includes, and shortcodes - Code samples in any language (tree-sitter; Roslyn dropped) - Search that lands on the right heading (DeweySearch) - Inspect your site from the command line (build + diag) - Social cards, generated per page - Turn your docs into a PDF (Pennington.Book) - Pennington 0.1.0, in beta - Color themes Verified with diag warnings: no broken links, xrefs, or front-matter errors.
|
🛰️ Docs preview: https://pr-57.pennington-dev.pages.dev Rebuilt on every push to this PR; torn down when it closes. |
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.
What this is
A tone-and-accuracy pass over the existing blog posts, plus backfill posts for what shipped after the launch batch.
The launch posts were written in one go and carry staged dates (April to May). The code kept moving through June, so several posts drifted from the current API. Each existing post was checked against source; the fixes are small and listed below.
Accuracy fixes
introducing-pennington,AddDocSitetakes aFunc<DocSiteOptions>, so the original snippet didn't compile.structured-data-and-accessibility, core now shipsJsonLdArticle,JsonLdPerson,JsonLdWebSite, andJsonLdBreadcrumbList, so "ships only one type" was wrong.llms-txt, the front-door header file isllms-header.txt, notllms.txt(a staticllms.txtthere would shadow the generated one).catch-broken-links, four auditors shipped (links, overlap, xref, translation), not two, and the "single source" mechanism claim is softened.api-reference-from-xmldocs, a duplicated how-to link is removed and the robots-only block is described as a declaration-only C# skeleton rather than plain HTML.build-report-and-dev-overlay,pennington-on-nuget,data-files-and-taxonomies,dotnet-new-templates, anddocumentation-in-every-languageget smaller corrections.New posts (2026-05-19 to 2026-06-22)
Verification
dotnet run -- diag warningsreports 0 errors, 0 warnings, 0 info: every xref resolves, internal links are valid, and strict front-matter parsing passes.Out of scope
The
.md-twins wording in thellms-txtpost (to match the{route}.mdchange) is left for the llms-twins work. This PR touches only the header-file line in that post.