Today, I came across one of my favorite bloggers’ GitHub profile, @Simonw . What caught my eye was the profile readme section, where Simon lists the latest posts from his blog.
Simon’s GitHub Profile
This content section seemed automated, so I inspected the repository and found that it indeed was. What impressed me (and reaffirmed my respect) was that there was a blog post 1 linked to this creative expression, explaining how it was made.
 |
|---|
| ➚ This beautiful screenshot was taken from my macOS app. Get it for yourself! |
It appeared that a significant portion of the content was hosted elsewhere (if not already on GitHub). All that was done was to compile everything neatly into one place.
My Existing System
Coincidentally, I also have a feed of my own, both live (where content is hosted on my publishing platform) and RSS-based. This meant that I could set up a similar dynamically generated readme system to showcase my content on my GitHub profile.
 |
|---|
| ➚ This beautiful screenshot was taken from my macOS app. Get it for yourself! |
So, I spent some time learning from Simon’s implementation and setting up a similar workflow.
The readme is generated as a cron task using a GitHub Actions Workflow. The key part is a simple script, less than 100 lines of Python .
My GitHub (New) Profile
You can find my current feed on my GitHub profile .
 |
|---|
| ➚ This beautiful screenshot was taken from my macOS app. Get it for yourself! |
It feels like an eye sore but I want to sleep on it.
The current design is very similar to Simon’s (with some noticeable tweaks), but it’s prone to changes with time and mood.
➡️ So now, everytime I tweet / post on X via my Content Publisher System, if it’s among the latest 10 posts (excluding replies and perhaps quotes), it’s prone to be part of this new ‘Latest Feed’ on my GitHub profile.
This was fun.