Read them in order. Each builds on the last.
Migrate the source, keep it current, connect it, generate from it, prove it, and scope it. Every project has a post, a design document and a repository, and each design document links to the running build.
Five posts. Each leads to a project.
From post to repository.
Each design document ends with a link to the running build. A hatched step means it is not ready yet.
Migrate DITA to docs as code and prove nothing was lost, with keys, content references and conditions kept as real reuse.
Builds on DRY and DITA reuse
A first-draft documentation pull request on every code merge, so the writer reviews a draft instead of starting from a diff.
Builds on docs as code
Answers that cross documentation silos by walking the links writers already keep, with every step cited.
Builds on Bush's trails
New DITA topics drafted from the ones you already have, with the schema acting as the guardrail.
Builds on information types
Regulator-ready evidence built from the DITA source and the approvals Git already records.
Builds on Grice's quality maxim
Answers scoped to the hardware generation a reader actually runs.
Builds on keys and profiling