Introduction
In the age of information overload, we’re all voracious readers, collectors of bookmarks, and lifelong learners. But if you’re anything like me, you’ve probably faced this: you save a fantastic article on dev.to, a must-read on daily.dev, and a handful of gems elsewhere—only to lose track of them when you need them most. The result? A scattered digital trail and a sense of missed opportunity.
That’s where the idea for my open source Reading List project was born: a single, reliable place to automate, curate, and share everything I’m reading—across platforms, in real time, and with the world.
The Spark: Solving a Real Problem
The inspiration was simple but powerful:
I wanted a way to find my bookmarks from different platforms, all in one place, whenever I needed them.
But I also wanted more. What if this reading list could be public—a living portfolio of my learning journey, a way to show the world what I'm reading, and maybe even inspire others?
This project isn't just about personal productivity. It's about storytelling through reading making your learning journey visible, discoverable, and shareable.
The "Now Page" Philosophy
This project draws inspiration from Derek Sivers' concept of the "now page"—a simple, public declaration of what you're currently focused on. Instead of a static "about me," a "now" page answers: What are you working on right now?
My reading list applies this to learning: What are you reading right now? It’s a living, breathing snapshot of your current intellectual journey—not what you read last year, but what you’re actively engaging with today. The beauty of this approach is its authenticity. It’s not curated for perfection; it’s real, current, and honest about where your attention is actually going.
From Idea to Architecture
The core challenge was integrating multiple data sources—dev.to, daily.dev, and potentially more—each with their own APIs and formats. I wanted a solution that would fetch and update my reading list automatically, without manual intervention, and make it public for anyone to see.
The answer was to use GitHub Actions as the orchestrator. On a schedule, it fetches data from all sources, normalizes it, and prepares it for publishing. The data is stored as simple JSON, which is then bundled with the site and deployed to GitHub Pages. This means my reading list is always up to date, always available, and always at the same universal path: {username}.github.io/readinglist.
By keeping everything automated and using GitHub’s infrastructure, the project is both reliable and easy for anyone to fork and adapt. No server maintenance, no manual updates—just a living record of what I’m reading, always fresh.
Roadmap
Here’s what’s next for the project:
-
More Data Sources
- Integrate with additional platforms like Pocket, Medium, and Twitter bookmarks.
-
Access to Browser Bookmarks
- Allow users to import or sync bookmarks directly from their browser, making the reading list even more comprehensive.
-
Enhanced Filtering
- Add advanced filtering and search, so users can quickly find articles by topic, source, or reading time.
Conclusion: A Universal Reading Path
What started as a solution to my own bookmark chaos has become something bigger—a platform for making learning journeys visible and shareable. The beauty of this project is its universal accessibility. Just like the "now page" philosophy, your reading list will be available at a universal path: {username}.github.io/readinglist. This consistent URL structure makes it easy for others to discover and follow your learning journey, creating a network of shared knowledge and inspiration.
Check out the live demo:
https://keshavashiya.github.io/readinglist/
Explore the source code:
https://github.com/keshavashiya/readinglist
If this resonates with you, fork it, customize it, and share your own reading journey. Let’s make learning—and sharing—more visible, more connected, and more meaningful.
Top comments (0)