Posted on 7 Comments

Rethinking Planet GNOME with GitLab Pages/CI

Some GNOME websites are getting modernized and simplified, but Planet GNOME has fallen behind. Not anymore. I started a prototype for a Python script to publish Planet GNOME with GitLab Pages/CI.

As Planet GNOME Editor, I am often asked to look for blog and syndication issues I couldn’t really address due to limited server-side access. With this, debugging indexing issues should be easier as it is just about looking at the CI job output.

Also, the Planet website is perceived as messy and outdated. So this work allowed Jakub Steiner to quickly jump in and restyle the page from a clean state.

Try it live at and let me know what you think. Keep in mind this is a proof of concept. Tips, feedback, and contributions are welcome in the project repo.

This still doesn’t produce the global Planet rss feed, just the webpage, but that’s in my TODO list too.

P.S.: I know feed readers/parsers can over-request rss/atom feeds. So I plan to cache data and use metadata to avoid redundant downloads before this is even considered as a replacement for the current Planet implementation. No worries. πŸ˜‰

7 thoughts on “Rethinking Planet GNOME with GitLab Pages/CI

  1. Looks nice! Though with larger fonts and Firefox on Android, the blue header is smaller than the text.

  2. I like it! Now I just need to get a proper hackergotchi πŸ™‚

    1. You mean avatar. Hackergotchis need to die. πŸ™‚

  3. Awesome work, both from you and from Jakub. Thanks for tackling this, the refresh is welcome.

  4. If you like fast systems and the environment, give forgejo (fork of gitea) a shot.

    Gitlab is really inefficient. 4GB memory at least (if you use docker and start the cli, add the amount for every cli) and the beast is slow as hell.
    Forgejo is so fast the browser lags behind the website (website is rendered but the browser needs its time) and need way less resources (and you have Github like CI actions).

    To the first thing, in my opinion, we waste energy and our own time with inefficient code for no reason than good marketing of some projects.

    1. Why does performance matter for rendering a static website that updates a couple of times a day only?

      This approach of using gitlab pages is for the sake of simplicity and maintainability.

      We’re not in the business of website development, we make a desktop and this is a tool to be used within our community.

  5. Great stuff! I would however recommend keeping a vertical separator among posts. Hackergotchis are big enough when scrolling on a mobile device, that they can be confused with any other image.

    It would be better to have an horizontal line or other clear separator among posts like it is now on Planet GNOME.

Leave a Reply

Your email address will not be published. Required fields are marked *