Skip to content

docs: rewrite all chapters in the Geewax house voice - #17

Merged
patterncatalyst merged 1 commit into
mainfrom
docs/geewax-voice
Oct 23, 2026
Merged

patterncatalyst merged 1 commit into
mainfrom
docs/geewax-voice

Conversation

@patterncatalyst

Copy link
Copy Markdown
Owner

Applies the approved writing voice across all 13 chapters: Geewax example-first teaching structure on Kubernetes-Patterns vocabulary. Concept leads with a concrete thing in the project before the abstraction; ch03 gets a before/after place_order code pair (#A/#B/#C). Zero em-dashes, no rule-of-three, no filler/meta/intensifiers; contractions, varied cadence, natural transitions. House spine kept; all code/commands/figures/output/identifiers preserved. Verified: 0 em-dashes, 0 ban-tier, guards + jekyll build clean.

Apply the approved writing voice across all 13 chapters: J.J. Geewax
example-first teaching structure on Kubernetes-Patterns-grade vocabulary.

- Lead each concept with a concrete thing in the project (a service,
  endpoint, method, command) before naming the abstraction.
- Add a before/after code pair in ch03 place_order (naive write-then-check
  vs. the real check-stock -> persist -> publish order) with #A/#B/#C
  callouts, built from the actual handler.
- Zero em-dashes (recast with commas, colons, semicolons, parentheses, or
  new sentences; figure-caption dashes become colons).
- No rule-of-three cadence, no filler or meta-sentences, no stacked
  intensifiers. Contractions, varied sentence length, natural transitions.
- House spine kept (Learning objectives / Why this matters / For deeper
  coverage). All code, commands, figures, output, and identifiers preserved.

Verified: 0 em-dashes, 0 ban-tier (lgtm-professional-voice), forbidden-syntax
/ cross-references / liquid-collisions clean, jekyll build green.
@patterncatalyst
patterncatalyst merged commit 31d171d into main Oct 23, 2026
1 check passed
@patterncatalyst
patterncatalyst deleted the docs/geewax-voice branch October 23, 2026 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant