Article structure
Why I Separate Blog and Projects
When I set out to update my website, one of the most fundamental changes I made was the clear separation between blog posts and project pages. This decision was not just about aesthetics or navigation, but about the underlying philosophy of how I want to present my work and ideas. The distinction between these two types of content is rooted in their purpose, structure, and the way they evolve over time.
Blog posts are inherently temporal. They capture thoughts, experiences, and commentary at a specific moment, often reflecting on current events, personal milestones, or technical insights. Each blog entry is stamped with a date, marking when it was published. This timestamp is not just a technical detail. It is a contextual anchor, giving readers a sense of chronology and progression. For example, when browsing the blog, one can trace the evolution of my interests and expertise, seeing how my perspective has shifted or deepened over the months and years. The date on each blog page is a signpost, guiding the reader through a narrative that unfolds over time.
Projects, on the other hand, are less about fleeting thoughts and more about enduring work. A project page documents a specific endeavor, whether it’s a software tool, a design commission, or a collaborative effort. While projects also have dates - often indicating when they were started, completed, or published - their relevance is less tied to the moment of writing and more to the lifecycle of the project itself. The date on a project page serves as a historical marker, but the content is meant to be referenced long after its initial publication. Projects are living artifacts; they may be updated, improved, or even archived, but their core purpose remains to showcase tangible outcomes and achievements.
This structural difference influenced my decision to separate the two during the website update. Previously, blog posts and projects were intermixed, making it difficult for visitors to distinguish between ongoing commentary and completed works. The lack of separation led to confusion: someone looking for technical guides or personal reflections might stumble upon project documentation, while those interested in my portfolio had to sift through unrelated articles. By creating distinct sections, I made it easier for readers to find what they’re looking for and to understand the context of each piece.
Another reason for the split was the nature of updates and revisions. Blog posts are typically static once published, serving as records of a particular moment. Projects, however, may undergo significant changes. New features, bug fixes, or even complete redesigns. By keeping them separate, I can update project pages without disrupting the flow of the blog, and vice versa. This modularity makes the site easier to maintain and ensures that each section remains coherent and focused.
The dates themselves tell a story. On the blog, you’ll notice a steady rhythm, with posts appearing at intervals that reflect my engagement with new ideas or events. The pauses between posts are sometimes short, sometimes long, mirroring the ebb and flow of inspiration and available time. On the projects pages, the dates are more sporadic, often clustered around periods of intense work or collaboration. These patterns reveal not just what I’ve done, but how I’ve balanced reflection and creation over the years.
Ultimately, the decision to separate blog and projects was about clarity, usability, and respect for the reader’s experience. It acknowledges that not all content is created equal, and that different types of work deserve their own space and structure. By making this change, I hope to provide a more intuitive and enjoyable journey through my website, one where ideas and achievements can be appreciated on their own terms, and where the passage of time is both visible and meaningful.