Some useful ideas do not fit neatly inside a project page. They start as questions about a decision, a method, or how one piece of work connects to another. The blog gives those thoughts a place to continue without making every project carry the whole story.
Let each format do its job
A project page should help someone understand a particular piece of work: its setting, my contribution, and the result. An article can take a wider view, tracing an idea across examples or sitting with a question that has no single project-sized answer. Keeping those roles distinct makes both easier to read.
Dates give ideas a shape
Publication dates let readers see when an idea was written and how the writing sits alongside the rest of the portfolio. A concise summary offers another useful signal: it says what the article explores before someone commits to reading it. Together, dates and summaries make a growing archive easier to browse.
Write toward a real question
I find a focused article more helpful than a broad declaration of expertise. One question, decision, or observation gives the piece a point of view and gives the reader something concrete to consider. The writing can then add depth to the selected projects instead of simply repeating their descriptions.
The blog works best as a record of thinking, not a second project gallery. When an article follows a question worth exploring and clearly signals what it contains, readers can move between the work and the ideas with purpose.