Skip to main content

Interfaces & Data

Interfaces​

InterfaceType
Static web UI (linux-genealogy.html + JS/CSS)Frontend
Local Python CLI scripts (compile-graph.py, generate_reference.py, scratch/*.py)Data pipeline
Filesystem datasets (JSON, JSONL)Data storage
Embedded analytics (gtag, Clarity)Analytics

Produces​

  • data/linux-genealogy/linux-genealogy-graph.json
  • js/linux-genealogy-graph-data.js
  • linux-genealogy.html
  • linux-genealogy-expanded.jsonl
  • linux-distros-reference.md

Consumes​

  • Scraped sources (Wikipedia/Wikidata markdown dumps)
  • Local filesystem inputs under d:\lg

Depends on​

  • Python
  • D3 (client-side)
  • Local filesystem (d:\lg)
  • External analytics endpoints (Google Tag Manager, Microsoft Clarity)
  • WDS governance artifacts (manifest inheritance)

Used by​

  • The operator (Herb), directly
  • The APTlantis website section at aptlantis.net/linux-genealogy
  • Internal research and reference workflows
  • aptlantis_net's src/features/linux-geneology/ feature area consumes this project's dataset/visualizer concept

Notable detail​

Both the raw scraped source (Wikipedia/Wikidata markdown) and the derived graph JSON are checked into the repo side by side — an unusually transparent provenance trail for a dataset project, letting anyone trace a graph node back to the exact source text it was derived from.