Visit the work
Where a public page exists, the first button takes you there. The GitHub link is always available too.
Start here
A clearer way to look around
GitHub is useful for code, but it can hide the story. This guide leads with public work, plain descriptions and the history that links projects together.
Follow every real connection
Open a project’s related-work list to see all evidence-backed public neighbours, not a token sample.
Read the history properly
The date on each card is the first substantive build evidence. It is not GitHub’s easily distorted latest-update label.
Freshly completed
New work, without losing the older roots
Loading the latest original builds...
Project shelf
Explore the complete public collection
Search by a project name, an idea, a family or a connected project. The filters use the project’s own history, not an accidental platform sort order.
Storylines
Projects that grow in sequence
These are documented progressions, not claims that a later project made every earlier one obsolete. Use them to understand where an idea began and where it went next.
Print directory
A handout-ready guide
Print this page as a small portfolio or event handout. Every entry carries its public address and a locally generated QR code that can be scanned.
Local and scannable: every QR code is generated from the entry's own public address inside this repository, not by a third-party QR service. The readable web address remains printed as a fallback. For the most reliable scans, print at 100% size rather than squeezing the page smaller.
How dates work here
Original work date, not housekeeping date
Loading the audit method...
What counts: the earliest audited commit with substantive project material, recorded in Brisbane local date.
What does not count: a later licence, standard template or small maintenance change that makes GitHub say a project was just updated.
When evidence is missing: the project says so instead of inventing a date.