Je travaille dans les communautés de logiciels libres (OSS) sur 
GitHub depuis plus d’un an maintenant et, bien que je pensais avoir trouvé tout ce à quoi je voulais contribuer, j’ai récemment découvert le projet personnel de 
Peli, action-continuous-translation. Je suis très heureux d’avoir commencé à y apporter des contributions régulières et de faire désormais partie de cette petite communauté.
Every great project starts with a realization of a problem. My GitHub profile README was cluttered, filled with too much information, too many badges, and an overwhelming amount of content that lacked style and structure. It had hackathon achievements, GitHub contribution graphs, various technical badges, and much more, making it visually unappealing and difficult to navigate. Initially, I thought this was an effective way to present myself, but over time, it became clear that the information was overwhelming rather than informative. I wanted something new, a more refined and visually appealing approach to presenting my profile, and the idea of implementing a bento grid came to mind. The goal was to create a layout that was not only functional but also aesthetically impressive and structured.
Creating a standout GitHub profile README isn’t just about adding a few badges — it’s about pushing technical boundaries. In this deep dive, I explore low-level SVG manipulation, HTML-to-SVG conversion, inline animations, and full automation with GitHub Actions to build what I believe is one of the most technically advanced GitHub READMEs. From a dynamic Bento Grid that updates every 5 minutes to embedding live SVGs without external requests, this project transformed my profile into a living, self-updating showcase of my work. Want to know how I did it? Let’s break it down. 🚀
Today we’ll take a look at how to set up a GitHub repository which will be deployed to a k3s cluster via Argo CD. In summary, the article will include Workflow files, Dockerfile, manifests (deployment) and 
Docker Hub repositories. Please check out our Argo CD blog because this will be a continuation of the other post.
