Roadmap
// loading…
// loading…
Hi. You're probably wondering why a portfolio has a roadmap. The honest answer is that I've been having too much fun building things for this site. At some point it stopped being a portfolio and turned into me, as a website. It is also the best proof I have of what I can build.
So this is what might come next. Loose ideas, nothing else. No dates, no promises.
// an idea that grows up leaves here and becomes a plan in docs/.
Standardize everything to "posts."
Not all of them have icons, so pick the best ones for the Home page so it doesn't get too cluttered.
Use https://recharts.github.io/ and add cool animations
As the log page grows, loading all items at once will slow it down. Implement pagination, a grid gallery layout, or a "Load More" button to keep the page fast and smooth. Could use: https://reactbits.dev/
Bigger than docs. A page like the roadmap that lists every widget on this site, each one with its documentation and with every state it can be in: loading, empty, error, and the one where everything worked. The hosted version comes from Velite, and the same docs live as markdown in the repo so they can be read straight from GitHub. Maybe a post or a project out of it: my portfolio widgets.
Building a self-hosted API to track personal finances so my data stays mine. It handles automated payment logging from my phone using secure tokens, with quick options to categorize expenses on the go or manage them later from a custom dashboard.
A page for my open source work, built after I start contributing to projects that aren't mine. An empty page would be worse than no page at all.
Let anyone leave a comment about the site without signing in, and show them somewhere. Every new one emails me. Same open-form problem as tipfy, so it needs the same protection. What I want is the Figma version of it: point at a card or a section, drop a pin on it, write there. The comment belongs to that thing instead of to a form at the bottom of the page, and the pins stay on screen as a trace of what people stopped on.
Tipfy is where people recommend music to me. I want to build a complete project around it: expand it beyond music to include movies, TV shows, and books, move the backend to Supabase, email me on each recommendation, protect the submission form, and add a link to this app on the /log page.
showEasterEgg in the titlebar fires a toast and that's it. Whatever it turns into, a toast isn't a reward. I don't know what the feature is yet.
State for every card and brand of the site, color, typography, tokens, do's and dont's, ...
A simple dashboard to track workout progress over time, focusing on weight progression per exercise and week streaks.
The home page got bento grid and cards and the rest of the site did not. Blog, projects, about, contact, all still lists of links in one column. I want them rebuilt the same way, so the site looks like one site. The clearest piece is posts and projects, which should read like a feed: one item per card, newest first, and maybe both in the same feed.
One feed for everything I finish: films, series, books, albums, podcasts, games. Catalog cards, drawn star ratings, filter pills that survive the server render.
Some of the components are dull. I want to make them better. First one up: the experience card becomes a browsable file tree of the site.
I want to add animations to the home page widgets so the site feels more alive. Something with a wow effect.
One type scale for every size on the site (UI Patter refactor)
It's react-github-calendar today. I want to drop the library and build it from the GitHub API myself, so the squares are mine to style and animate.
The Apple Watch rings on the home page, fed by a Shortcut that pushes the day's numbers into Postgres.
A card that reads this file and shows the items as a checklist, ticking off what's done. I don't know yet where it goes: home, about, or its own page.
CRUD for the log behind WorkOS plus an email allowlist checked at the route, not only in the proxy matcher. Anyone else gets a 404.
The site has real features now, with CRUD, auth and a database behind them, and none of it is tested. I do not know what I will use yet. Maybe Vitest for the small pieces and Playwright for the flows.
Once the big refactor is done, measure the site again with Lighthouse and compare it against what it scores today.