The isolated knowledge problem
You publish a strong runbook. Six months later nobody finds it, and the related lab is unlinked. Content dies in silent lists.
This third demo article shows how to connect pieces: takeaways, see-also, footnotes, captioned figure, and a clear exit CTA.
Figure with caption (click to enlarge)
Figure 1 — A DailyOps article as a node in the knowledge graph (lab, runbook, product).
The caption renders under the image. Click opens an overlay for large-screen reading.
Nuance via footnotes
Redundancy is not a node count1. Likewise, a triage SLA is not a business SLA2. Footnotes hold that nuance without bloating the main paragraph.
See also (internal links)
The block below is addressable as #see-also-internal-links (shareable deep link into this section).
You can also link inline, such as theoretical redundancy, when the narrative needs it.
One CTA at the end of the path
Too many buttons at the end means no click. Pick one action: open a lab, subscribe, or contact.
Demo series recap
| Article | Featured reading UX |
|---|---|
| Long-form navigation | TOC, progress, anchors, Focus, A±, takeaways |
| SSH runbook | Code + copy, checklists, tables, callouts |
| Knowledge graph (this one) | Takeaways, figure, footnotes, see-also, CTA |
For implementation detail (files, markdown syntax, backlog), see docs/ARTICLE-READING-UX.md in the repo.
Notes
- Two firewalls on the same core switch are still a single point of failure.
- A P1 “active exfiltration” and a contractual 99.9% uptime are measured differently.