A portfolio is a page, not a project
Most unbuilt portfolios die the same way: it starts as "I need a portfolio site", becomes a decision about frameworks and hosting and domains, and then sits on the list for two years while the actual projects pile up unseen. The version that gets finished is a single page with one card per thing you made. What it is, what it is built from, where to look at it. That is genuinely all a person needs to decide whether they want to know more about you. Below is that shape, filled in with placeholders. Swap them for your builds.
What it does
A small servo-driven robot that sits on the desk and reacts to whoever is in front of it. Currently at the "moves reliably" stage, not yet the "looks finished" stage, which is worth saying out loud rather than hiding.
Built with
ESP32, three hobby servos, a printed shell, and far more hot glue than the photos suggest. Firmware in C, control script in Python.
What every project card actually needs
One sentence on what it does, written for someone who has never seen it
What it is built with, so a reader can tell if it is their kind of thing
A link to the code, the demo, or a photo. Any one of the three beats none
Its honest status: finished, in progress, or abandoned and still interesting
This page is a file in a Git repository. You edit it in your editor, commit it, push it, and the page updates itself. There is no dashboard to log into and no export to worry about later: the content is markdown-ish text you already own, sitting next to the code it describes.
Abandoned projects belong here too. A shelf of half-built things is a more honest portrait of a maker than three polished pieces, and it is usually the one people want to talk to you about.
"The best portfolio is the one that exists.
"Steph11th of August 2026