When small project cards stop explaining enough
My first portfolio fitted on one page: an introduction, skills, a few projects and contact details. That suited what I had to show. Professional experience, recommendations and more developed projects brought a question beyond available space: what could someone actually understand about the work before leaving? More content would not automatically produce a clearer answer.
A card with a name, screenshot and technology list identifies a project. It says less about the original need, my role or the decisions involved. DevFlow and Practicora work with different data and workflows. Giving them identical technical summaries would hide exactly the parts that deserve a more careful explanation.
Let a visit move at two speeds
The homepage therefore provides an overview, with dedicated pages for more detail. That first level still needs to show concrete work: a product preview, the problem addressed and a clear link. Someone in a hurry should understand the outline without opening every case study. Another visitor should have space to follow the reasoning further.
In the October 2026 redesign, homepage previews become more generous. Case studies keep their role for features, screenshots and technical decisions. The challenge is to make the move between those levels feel natural, without repeating every paragraph or leaving the homepage too abstract to give anyone a reason to continue.
A screenshot needs an explanation
An interface can look pleasant without making its purpose clear. DevFlow’s Today page means more when someone understands that it connects priorities, focus and the agenda around a local workspace. Practicora’s journal becomes clearer through its relationship to history and reports. A caption should contribute that connection rather than only describe the visible screen.
I also want to distinguish what is visible, what has been developed and what remains a direction for future work. Both projects are in active development. Accurate presentation includes their limits as well as their features. A useful portfolio creates room to discuss a decision without turning every screenshot into a promise about the finished product.
Connect four sites without four separate introductions
The personal site, portfolio, resume and blog have related purposes at different levels of detail. The personal site gives a brief introduction. The resume offers quick reference points. The portfolio explains the work, while the blog develops a question. A shared identity helps someone recognise the person behind these different ways of reading the same background.
The facts need to stay consistent: titles, dates, project status and links. Wording can change with its purpose without changing the underlying story. A short description does not need to contain everything. It should prepare an accurate next step, so the details found through a link match what the introduction led someone to expect.
Check the route as well as the page
Separate URLs make it possible to share a project or experience directly. Each page then needs to make sense without a visit to the homepage first. Titles, metadata, the route back to projects and related links all belong to that journey. Navigation contributes to the presentation even when it is working quietly in the background.
Responsive layouts and accessibility require the same attention to context. A gallery and a long explanation are read differently on a small screen. My criterion for this redesign is straightforward: after a short visit, someone should know what I build, what part I take in it and where to find the details that interest them.