Repository navigation
Glossary: one page per letter, one trimmed glossary with an anchor per term - #3
Merged
Merged
Conversation
Merge technical-documentation's six letter-group pages and site-web-content-src's one-file-per-term glossary (the same content) into an index and six letter-group files: 1,060 terms, each a ### heading. Every entry is rewritten in plain British English (the sources were mostly Wikipedia, CxOne and Agile Alliance text) and trimmed from 104k to 34k words. Third-party images are dropped; eight diagrams are redrawn in Mermaid. redirects.tsv maps every old tarf.co.uk term page and old technical-documentation anchor to the new page and anchor. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
markbac
pushed a commit
that referenced
this pull request
Oct 19, 2026
The glossary move (#3) left out its 237 images. They are back: 241 references in 205 terms, 235 image files in content/glossary/images/, from technical-documentation's glossary. Each sits after its term's definition, with the term as alt text and a caption. Terms that were renamed or merged get their images through the redirect map. Not restored: the NBAP entry's hotlinked everythingrf.com picture (external, not a file in the repository), and the images of L2S and MPS, terms the glossary dropped. Most of these images are third-party (Wikimedia, BT and Openreach, vendor and lecture slides), restored on the owner's instruction. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
markbac
added a commit
that referenced
this pull request
Oct 19, 2026
* Publish the primers section on both sites PR #4 moved the primers in but did not add them to site.documents, so neither site showed them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Templates: add 16 templates from docs-WoW and the NFR scenario from EngineeringProcess New: project vision, architecture vision and principles, crosscutting concerns, software design specification, traceability matrix, test plan, decision log, meeting minutes, lessons learned, release plan, risk register, SBOM, systems engineering management plan, team working agreement, technical debt register, NFR scenario. Each follows the section's pattern: an introduction, then the template in a fence. The other ten docs-WoW templates were already covered (ADR, RFC, the canvases, postmortem, experiment record, interface specification, architecture document, requirements). The index groups the templates by project stage. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Guidelines: move in EngineeringProcess's 26 guidelines and supporting pages, and publish the section - EG-001 to EG-026, core rules, combined checklists, agent rules, organisation adoption, personal projects, the business principles overview and the principles catalogue. - File names drop the eg-NNN- prefix; each page gets an H1 with its ID. Links to templates-reference now point to the Templates section. - EG-014 gains VCS-15 (imperative subject under 72 characters, a body that says why), the one rule GU-014 had that EG-014 did not. GU-015's PR format was already covered by EG-015 and the pull request template. - EngineeringProcess's AGENTS.md becomes a template, since the guidelines tell readers to copy it. - Seven sentences over 30 words split to clear the lint warnings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Standards: move in technical-documentation's specialised GU documents, and publish the section C coding standard, MISRA C, Python for supporting tools, software architecture principles, API design, unique identifiers, LwM2M objects, IoT device architecture principles, battery budgeting, constrained binary payloads, offline storage, and serialisation and factory test. - Word-based file names and shorter sentence-case titles; the old GU numbers are dropped. - GU-009 is technical-documentation's single-file C standard. wip's 11-part split is not published: it draws on an employer's internal standards. - en-GB spelling in prose (not in code), long sentences split, heading levels fixed so each standard is one chapter in Word and PDF. - Mermaid labels with brackets quoted, and semicolons removed from sequence messages, so the diagrams render. \text in maths becomes \mathrm, because py-doc's PDF template has no amsmath. - Six links point at guides that the guides commit adds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Guides: move in technical-documentation's guides, the how-to GU documents and the docs-WoW team guides, and publish the section - Six guides from technical-documentation, each in its own folder with numbered chapters: C4 modelling, cyber security, IoT endpoint and gateway architecture, IoT fleet operations, HIL and automated testing, scaling architecture. The architecture handbook moves separately. - Single-page guides from the how-to GUs: ADRs and RFCs (GU-005 and GU-006 together, their templates now pointing to the Templates section), software design specification, high-level design, architecture review board, agile requirements, defects and debugging, and code review (GU-011 plus docs-WoW's roles section; its PR template points to the Templates section). - Git: GU-013 with docs-WoW's branching strategies and version control chapters. docs-WoW's other Git guide (git.md) covered the same ground as GU-013 and is not moved. - Ways of working: docs-WoW's eight team guides as one guide. - Clean-ups: emoji out of headings, :::mermaid blocks fenced, heading colons and skipped levels fixed, en-GB spelling in prose, 70 long sentences split, Mermaid labels quoted, C4-PlantUML from PlantUML's standard library, the C4 tooling section now uses py-doc c4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Handbook: move in technical-documentation's architecture handbook, and publish the section - The eight chapters keep their numbers; titles in sentence case. - Chapter 3 gains a section on message queues and publish-subscribe, the one topic in site-web-content-src's older handbook that this one did not cover. The rest of that handbook is the earlier version of the same eight chapters and is not moved. - C4-PlantUML includes use PlantUML's standard library; long sentences split; en-GB spelling. Also across the sections moved so far: - Links and mentions that still named a GU number now use the title of the page that replaced it, and links to the Git guide point at its folder. - Mermaid cylinder shapes ([( )]) that an earlier clean-up had turned into boxes are restored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tech Radar: move in technical-documentation's radar, and publish the section and the interactive chart - The section: the methodology (from overview.md) as the section page, the four quadrant pages and the directory of all 77 entries. It builds as Word and PDF like the other sections. - The interactive SVG chart (ADR-003: vanilla JavaScript, no outside dependencies) is HTML and script, so it is a site page of its own, site/docs/radar-chart/, listed under site.pages. - The chart's links went to technical-documentation's layout (GU files, primers by area, the old guide folders). Each now points at the page that replaced it, as a site URL; all 47 resolve. - site-web-content-src's TechRadar app (Next.js) is the older radar and is not moved. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Firmitas: move in Firmitas 2 from docs-WoW, with the first edition's appendices, and publish the section - The book as written: preface, acknowledgements, introduction, and Parts One to Three with their 29 chapters, each part in its own folder and each chapter numbered. - Firmitas 2's Appendix was empty, so it takes the first edition's Appendices A to G, and the first edition's Sections V (practice across disciplines) and VI (quality, regulation and assurance) as Appendices H and I. The second edition has no chapters on those subjects yet. - Left behind: the rest of the first edition (rewritten as Firmitas 2), Firmitas_Framework.md (the first edition in one file), cornerstone*.md (the framework's earlier name), the draft essays (the second becomes a blog post) and plan.md (a work plan, not for publication). - Mechanical fixes only, since this is the author's own prose: the manuscript header in Chapter 2, heading levels, four spellings, and the cone of uncertainty image, which had not been copied. The style warnings stay: 779 sentences over 30 words, three 'in order to', one heading ending in '!' (a book title). - The front page carries the CC BY-NC-ND 4.0 licence notice and the cover. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Blog: move in blog-tech's unpublished posts and docs-WoW's leadership essay, as written - Networking and home lab series: the 30 posts from wip/, dated 25 April 2025 in the order wip/list.md planned, each marked with its part number, plus a series page listing them (two planned posts were never written and are listed as such). - Home lab: the four tech_blog posts, 11 March 2025. The real internal addresses and domain are replaced with documentation values (192.0.2.x, home.example). - Architecture flashcards and the embedded architecture process mind map, 18 February 2025. - An Approach to Engineering Leadership and Delivery, 28 December 2025, leading into Firmitas. - The software design specification post takes the longer version of its text (SDS-wip.md), under the same date and slug. - Mechanical fixes only: titles as H1, heading levels, the excerpt marker, a post that was wrapped in a code fence, five spellings, a shorter slug. Style warnings stay (32 long sentences). - Not moved: planning notes (the docs-as-code series outline, the blog idea lists). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Guides: add wip's eleven explainers as Deep dives CBOR, CoAP, LwM2M, NB-IoT and cellular, certificates and keys, RTOS internals, SysVars, MISRA C, static analysis, Git internals, and docs, diagrams and architecture as code. Moved as written: mechanical fixes only (one hardware reference removed from the NB-IoT page, heading levels, spelling), so their 264 long sentences remain as warnings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Glossary: one page per letter, then Numbers and Symbols The six letter-group pages (a-c to s-z) become 26 letter pages, numbers.md (5G, 802.11 and the other terms that start with a digit) and symbols.md (.NET). Each term is now a ## heading on its letter's page, with the same anchor as before. - Every link between terms follows its term: 1,336 cross-page and 691 same-page links checked, none unresolved. - redirects.tsv: the 1,135 rows that pointed at a group page now point at the term's letter page; six new rows send the old group pages to the glossary index. - The index lists the pages with their term counts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Glossary: restore the original images The glossary move (#3) left out its 237 images. They are back: 241 references in 205 terms, 235 image files in content/glossary/images/, from technical-documentation's glossary. Each sits after its term's definition, with the term as alt text and a caption. Terms that were renamed or merged get their images through the redirect map. Not restored: the NBAP entry's hotlinked everythingrf.com picture (external, not a file in the repository), and the images of L2S and MPS, terms the glossary dropped. Most of these images are third-party (Wikimedia, BT and Openreach, vendor and lecture slides), restored on the owner's instruction. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Mark Bacon <streakyb@gmail.com> Co-authored-by: Claude Opus 5.5 <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
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.
Moves the glossary in from
technical-documentation/docs/glossaryandsite-web-content-src/Glossary/srcas one py-doc document: an index page, one page per letter (a.mdtoz.md) andnumbers.mdfor terms that start with a number or symbol. There are 1,060 terms, each a##heading with its own anchor.py-doc build glossarymakes one PDF and one Word file of the whole glossary.The two sources
They are the same glossary in two shapes.
technical-documentationhas it as six letter-group pages (1,081 terms);site-web-content-srchas it as one file per term (1,093 files), which tarf.co.uk served as one page per term under/Glossary/. 778 shared entries are identical once whitespace is normalised; the other 273 differ only by typo fixes, line wrapping and image references.authorriative Answer,dotNET,GBE - GE,Tcl-tk,CUE).G.729(an empty file),Csharp(a duplicate ofC#), the per-letter index pages, and eight.tmpAsciiDoc leftovers.Provenance
content/glossary/index.mdtechnical-documentation/docs/glossary/index.md, rewrittencontent/glossary/<letter>.md(a to z)technical-documentation/docs/glossary/{a-c,d-f,g-k,l-n,o-r,s-z}.md, andsite-web-content-src/Glossary/src/<letter>/*.md. µ-law (src/μ/) is now "Mu-law" inm.mdcontent/glossary/numbers.md.../docs/glossary/s-z.md, and.../Glossary/src/{1,5,8}/*.mdcontent/glossary/redirects.tsvweb-content/Glossary/**/index.html(tarf URLs) and the old headings (technical-documentation anchors)py-doc.ymldocuments.glossary.sourceslists the seven files in orderWhat changed in the text
MNCdescribed the BNC connector (now the Mobile Network Code);CLFdescribed the SLF;UTF-16described UTF-32;IPv4andIPv6had each other's expansions;NBAPhad NB-IoT text appended (NB-IoT is now its own entry).../guidelines/GU-0xxand../guides/architecture-handbook/.... Those sections are moving in parallel, so I left the links out (see the questions below).<!-- vale PyDoc.Spelling = NO -->switches.Encyclopaedic material left out
Most of it was Wikipedia, so it is better linked than kept. The entries that lost the most were Linux (distribution list), NGN, Mediation, VHDL, SS7 (national variants), Softswitch, RRC (state machine), FIPS 140-2 (security levels), WIN-T (increments), Capability Maturity Model (key process areas), Unicode, Jitter buffer, Latency, packet sniffing, NoSQL, Risk-Reward Matrix, SystemX (concentrator internals) and the codecs (bit-rate tables). Code samples went too: the BNF postal address grammar, an SGML DTD, a WSDL document, the SemVer grammar and the Gherkin examples. If any of these should live on as a primer or reference page, they would be written fresh there.
Dropped, and why
images/folderRedirects
content/glossary/redirects.tsvhas 2,182 rows (old_url,redirect_from,redirect_to,note). I have not changedmkdocs.yml./Glossary/, such ashttps://tarf.co.uk/Glossary/a/AES/→glossary/a.md#aes. Theredirect_fromandredirect_tocolumns are already in the formmkdocs-redirectstakes forredirect_mapsinsite/mkdocs.tarf.yml. Note that the old paths use a capital G.https://markbac.github.io/glossary/a/#aesandhttps://tarf.co.uk/glossary/a/#aes.Checks
py-doc lint content/glossary --strict(built-in rules and Vale 3.15.2): 0 warnings or errors.py-doc build glossary:build/glossary.docxandbuild/glossary.pdf(176 pages, a chapter per letter).py-doc site build: both sites build. A script checked every anchor link in the built glossary pages: 1,060 term headings and 5,263 links on each site, 0 broken.py-doc problems found (not fixed here)
diagrams/render.py_tools_revision()reads every entry ofpy_doc/diagrams/tools/. pip's__pycache__folder is one of them, so the build fails with PermissionError on Windows and IsADirectoryError on Linux. I deleted that folder in my local venv to build. The glossary has eight Mermaid diagrams, so this PR's "Word and PDF files" step will fail until py-doc skips non-files.d.md#dnsstays an external link, and the glossary has 1,530 links between letter pages. The sites rewrite them correctly; same-file links work everywhere. py-doc should turnother-source.md#idinto#idwhen it combines the sources.{#id}), and MkDocs re-slugs them. So the content uses MkDocs' slug as every anchor, with an explicit id only where pandoc's own would differ: 36 headings, such asASN.1 {#asn1}andC# {#c_2}.toc_depthin front matter does not shorten the PDF's contents, which list every term .Questions for Mark
site/mkdocs.tarf.ymlin a follow-up? That adds 1,094 small redirect pages.🤖 Generated with Claude Code