Add draft post: I made my book accessible by writing it like software - #1950
Open
benbalter wants to merge 1 commit into
Open
Add draft post: I made my book accessible by writing it like software#1950benbalter wants to merge 1 commit into
benbalter wants to merge 1 commit into
Conversation
Follow-up to "How I over-engineered my book" (PR #1949): a focused post on how authoring the manuscript in semantic Markdown and gating every build on axe-core/Playwright, EPUBCheck, and Ace by DAISY produces an accessible book by default rather than via a last-minute audit. Shipped as a draft (published: false) so it stays out of listings, the feed, and route generation until flipped. Links back to the flagship post; ported from a private book-repo draft and de-duplicated so the two posts complement rather than repeat each other. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
What
Adds a behind-the-scenes blog post: "I made my book accessible by writing it like software." It's the follow-up teased at the end of #1949 ("How I over-engineered my book") — the argument that accessibility falls out of two upfront decisions (authoring in semantic Markdown, gating the build on automated a11y checks) rather than a last-minute audit.
src/content/posts/2026-08-10-i-made-my-book-accessible.mdDraft, not live yet
published: false— keeps it out of listings, the feed, sitemap, OG generation, and route generation (getStaticPathsfilters onisPublished) until flipped. Flip topublished: truewhen ready to ship.How it relates to the flagship post
/2026/08/03/how-i-over-engineered-my-book/instead of re-deriving the "wrote it like software" premise, so the two posts complement rather than repeat.benbalter/book#1965, now superseded — safe to close) and trimmed: distinct opening hook, the shared "book as build target" setup collapsed to one linked sentence.Follow-up (one manual step, intentionally deferred)
The flagship footnote forward-references this post in prose but is not hyperlinked yet — linking a live post to a
published: falsedraft would 404. Once this merges and flips topublished: true, add the reciprocal link from the flagship footnote's "getting its own post" to/2026/08/10/i-made-my-book-accessible/.Checks
AIPatternshits. Remaining remark warnings are dictionary noise (WCAG, EPUB, reflows) and the incrementing ordered-list style used elsewhere on the blog.🤖 Generated with Claude Code