About Ubigraph Lab

What this site is

Ubigraph Lab is a small reference and notebook site organised around graph visualisation - specifically the Ubigraph environment, the demos that explain it, the documentation that surrounds it, and the related papers from scientific C++ that show up in the same conversations.

The site has three jobs:

1. Keep the strongest historical Ubigraph pages alive at their original paths.
2. Add modern landing pages on top that are useful to read in their own right.
3. Provide companion notes for the paper references that orbit the toolchain.

That is the whole intention. There is no ambition to grow into a general programming property or a community hub.

Who this is for

The site is written for three kinds of reader:

• Developers with a working memory of Ubigraph who are trying to understand or revive an old workflow.
• Researchers and students looking for graph visualisation demos, graph drawing concepts, or short paper references.
• Engineers who never used Ubigraph but want to learn how a graph viewer with a remote control protocol works, or what to use today instead.

The tone is the same for all three. There is no separate beginner track and no separate expert track. The pages try to be readable without being thin.

What the site is not

It is worth being explicit:

• This is not the official Ubigraph project page. It does not represent the people who built the original tool.
• It is not a download portal. No binaries from the original distribution are hosted here.
• It is not a community hub. There is no forum, no chat, no live issue tracker.
• It is not a general programming blog. Lab notes here are tied to graph visualisation or the surrounding toolchain.

That list is short on purpose. Telling you what the site is not is one of the more useful things this page can do.

How content is maintained

Pages on this site are revised in small batches when a question, a correction, or a useful new note comes up. The changelog is the record of visible changes, written in the same calm tone as the rest of the site.

A few principles guide the writing:

• If a claim cannot be supported by visible historical material, the page says so.
• If a PDF has not been verified, the page says so.
• If a demo is best understood by reading rather than running, the page says so.
• If a modern substitute is the better path, the page says so.

That last point matters more than it sounds. A site that exists to keep older material readable has a duty to point at current alternatives where the alternative is more useful.

Editorial standards

All copy on the site is written to a small set of internal standards:

• Plain English where possible.
• No filler transitions.
• No invented experience or fabricated case studies.
• No inflated claims about original Ubigraph status.
• No attribution to specific people or organisations beyond what visible historical material supports.

Where pages take a position, they back it up. Where pages are uncertain, they leave room for the reader to make a different call.

Why the historical URLs still exist

The historical paths under /ubigraph/ are preserved deliberately. Old links lead to real pages. That is partly a matter of respect for the people who linked to the original material, and partly a matter of giving readers a stable place to land.

There is no banner on those pages saying they have been moved or restored. There is no need. The page at each historical path is a complete, current page on the topic that path used to cover.

What you can expect when something changes

Site changes are visible. The changelog is updated when a page or a structural piece of the site changes. Routes that have stood for years do not move without a strong reason. PDFs at their original paths are not relocated to fashion-friendly URLs.

If a paper PDF is replaced with a verified version, the change is recorded. If a demo write-up gains a section because a question came up enough times to deserve a permanent answer, the change is recorded.

How to get in touch

The contact page is the right route. There is no ticket system and no formal SLA. Substantive questions get substantive answers when they arrive.

For ongoing reading, the most useful pages are usually:

• Ubigraph pillar
• Demos
• Docs
• Papers
• Lab notes

What you will not see here

A small set of things you will not find on this site, listed once so they are clear:

• Endorsements, partner badges, or affiliate content.
• Email collection forms or popups.
• Live community claims.
• Promotional language about the toolchain.
• Promises about uptime, support response, or future development of the original Ubigraph project.

The point is not minimalism for its own sake. The point is to keep the page about the topic.

A final note

The honest framing of this site is the one in the title bar: a working notebook for graph visualisation and dynamic networks. That is the right level of expectation. The pages are written carefully, the routes are preserved deliberately, and the editorial direction will keep pointing at the topic.