After several years blogging about open source development, UX, and sustainability, I've accumulated over 20 posts of varying depth and detail. The content was there, organized by date and tagged as I wrote it. However, looking at my blog from a reader's perspective, I realized the organization didn't match how people would actually want to use it.
Someone visiting my blog might be thinking: "What should I consider before starting a new open-source project?" or "Am I solving a real problem or just building what interests me?". They also may find one helpful post and scroll through the timeline hoping to find similar content. They won’t be thinking "What was published in May 2024?”.
I needed to make this content support learning better.
Instead of just organizing by tags (UX, frameworks, AI) or by date, I tried also organizing by reader challenges – the specific problems people are trying to solve when they come to my blog.
This led to creating "blog topic packs", small collections of 4–5 related posts grouped around a specific challenge readers face.
My first three packs:
🌱 Sustainable Open Source Projects Pack – Build projects you can maintain in the long run
🎯 Project Clarity Framework Pack – Keep projects focused for both developers and users
🧡 Building Open Source with Heart Pack – Foster projects that users and contributors enjoy
Each pack includes a brief intro explaining what you'll learn, then 4–5 posts that work together to address that challenge.
For readers:
✅ Know exactly what they'll learn before investing time
✅ Find relevant content quickly based on current challenges
✅ Get a coherent learning path instead of scattered posts
For the author: