Small useful tool
A compact project that removed an annoying manual step. Replace this sentence with the problem, your approach, and the useful result.
Things made, maintained, automated, overthought, or kept alive longer than expected.
The structure is ready for screenshots, source links, short case studies, or one-sentence entries. The strongest version says what changed because the project existed—not just what technology it used.
A compact project that removed an annoying manual step. Replace this sentence with the problem, your approach, and the useful result.
A good place for a sanitized infrastructure story: what was confusing, how you made it legible, and what became easier afterward.
Use this for a strange prototype, research idea, or technical rabbit hole. A sketch and honest notes are enough; it does not need to be a product.
A project can be represented without publishing its internals. Explain the service, your responsibility, and the constraints you designed around.
Diagrams, interfaces, generative work, or a physical build fit here. Link it to the Art section when the categories overlap.
Leave one slot visibly open. It signals that the collection is alive and gives unfinished work somewhere to land.
This page can stay selective while GitHub, Forgejo, or another repository host carries the exhaustive history.