Maintenance
Changelog
A small, ongoing record of visible changes to the site. Demos refined, docs corrected, paper notes expanded, paths preserved. The point is to keep the visible state honest.
How to read this page
The changelog records the visible changes to pages, structure, and reference material on this site. It is written in the same calm tone as the rest of the site. Entries are grouped where dates are uncertain, and dated more specifically where the date is confidently known.
Recent maintenance
Demo write-ups
The three core demo pages - random graph, random binary tree, and animation - have been revised. The write-ups now read as standalone explanations of what each demo is meant to expose, with a stronger emphasis on layout behaviour over time rather than any single still image.
The demos section landing page and the demo index were updated to point at the revised write-ups and to give a clearer reading order for newcomers.
Documentation refinements
The docs index and the modern docs section have been revised. The call surface section is now compact and consistent across both pages, and the practical notes on running older example code with current Python tooling have been moved up so they are easier to find.
A short worked example using xmlrpc.client from the Python standard library now sits alongside the call surface, where readers can see the shape of a working client without needing to leave the page.
Paper shelf companion notes
The papers section and the three companion notes - Blitz arrays, C++ templates as a Turing-complete language, and the Veldhuizen thesis - have been revised. Each companion note is now clearer about what it does and does not represent. Where a PDF is a careful placeholder, the companion note now says so explicitly. The corresponding historical PDF paths continue to resolve.
Downloads guidance
The modern downloads page and the historical downloads page have been updated to set realistic expectations about running older viewer binaries on current systems. The guidance on safer paths - using the documentation as a specification, building a stub server, or moving to a modern substitute - has been expanded based on questions that come up repeatedly.
Structural notes
Path preservation
All historical Ubigraph paths under /ubigraph/ continue to resolve. That includes the demo pages, the docs index, the downloads page, and the three paper PDFs. The decision to keep these paths in place is deliberate. Old bookmarks should keep working.
Modern landing pages
The site now keeps a small set of modern landing pages on top of the historical structure. These are demos, docs, downloads, papers, and lab notes. They link out to the original paths and are written to stand on their own.
Navigation
The top navigation has been kept short on purpose. Home, Ubigraph, Demos, Docs, Papers, Downloads, Lab Notes, FAQ. Anything more was creating friction in early reading tests.
The footer carries the supporting pages: about, contact, changelog, license, privacy, terms, support, sitemap. There is no external navigation in the footer.
Editorial notes
Tone
A pass was made across the site to remove filler transitions, to vary sentence lengths, and to keep the writing direct. The intended voice is that of a careful technical notebook: useful, calm, and honest about uncertainty.
Banned phrases
A small lint pass was added to keep promotional or misleading language out of the rendered output. The intent is not to remove all colour from the writing. It is to remove the kind of phrasing that would make this site sound like a launch announcement rather than a working reference.
Image discipline
Pages now use at most one image each, in JPG, with practical alt text. Images are referenced in a manifest used for production work and not exposed as a live URL.
Lab notes
The lab notes section holds longer write-ups that did not fit neatly inside the demos or docs:
- Ubigraph server and graph streaming
- XML-RPC graph control
- Graph visualisation alternatives
- Random graph layout notes
- C++ template papers and graph tools
These notes are intended to be revised as questions come in. The notes are not dated in a way that suggests a hard publishing calendar.
Maintenance approach
There is no fixed publication cadence. Updates are made when something on a page stops matching what people see in practice, when a correction comes in, or when a question comes up often enough to deserve a permanent answer on the relevant page.
The principles guiding the maintenance work are simple:
- Keep the historical paths alive.
- Keep the modern landing pages useful.
- Keep the companion paper notes honest about what they are.
- Keep the language plain.
Where to read next
If you noticed something on a page that should be added to this list, the contact page is the right route.