Closed on the forge: #3 superseded by the item renditions plan on #19, #6 folded into the genealogical vine #99, #9 folded into the publication mark #24. tp roadmap archive moved them to changes/ fragments. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2.1 KiB
2.1 KiB
Roadmap
Milestones for i.bytestone.uk. Each item is an open issue labelled
roadmap on git.bytestone.uk/hum3/life-weaver; tp roadmap add files
one, tp release retires those whose stories have shipped.
Demo
Victoria Drummond and her family, served from the shared static host.
Richness
What a page can carry beyond the record: pictures, maps, citations, trees.
- #4 Timelines and voyage maps from the lecture's boat2map charts
- #5 Citations: sources as structured references, footnotes in the biography
- #98 The vine of life: a person's left margin grown from their record, one stem from birth at the foot to death at the head, the years along it, flowers at the events
- #99 The genealogical vine: a person's right margin as a sparser vine of their kin from the register, ancestors up the stem, siblings as leaves, children as buds
Scale
From a handful of YAML files to many lives.
- #7 Records move from YAML files to Postgres (go-postgres), the files becoming an import
- #8 ID allocation: next free number, reserved ranges, redirects for merged records
- #10 Search and an index by name, place and year
- #81 Search past 45,000 people: names folded once at load (a scan to ~3M), then an index by key or a database column of the folded words (research/search-scaling.md)
Archive
The bytestone archive on the NAS as the primary store (docs/archive.md); stage 1 is #22.
- #24 Build on the NAS and publish NAS → site; a publication mark per person so only changed people are rebuilt and sent
- #25 Past 1–2 TB: items sharded by id prefix, the monthly fixity run, the offsite copy
Own infrastructure
i.bytestone.uk on its own host, no longer rebuilt as a static site.
- #11 i.bytestone.uk on its own host, pages served from the database rather than rebuilt
- #12 Image storage and a CDN
- #13 Backup and restore for the register
Interaction
Readers who can add to the record, and find themselves in it.
- #14 Suggesting a correction or an addition to a record
- #15 Accounts, provenance of every edit, and review before publication
- #16 A signed-in user's own place in the register, and kinship diagrams to any person drawn in the browser (wasm)