Skip to main content


This research covers updating so it's more readable & usable to our users.

Current status

Well, we're not happy with the present website. Usability is lacking, for more info see Raw meeting notes.

There are multiple tasks ahead of us to improve the website:

  • Layout
  • Structure

What to do?

Let's talk about the details - what we can do?

"Steal" osbuild's website

Hunor really likes Gotta say I (Tomas) like it as well - it's simple, clean, readable, convenient. The problem is that the website is not using a theme, it seems the team created it from scratch, for Jekyll.


  • Switch from hugo to jekyll
  • Copy-paste the osbuild site sources
  • Port to the new layout

Pick a different layout

Since the present layout has so many deficiencies, it's unrealistic to fix all of them. It is more efficient to move to a more usable layout.

The layout digitalcraftsman/hugo-alabaster-theme is pretty popular among python projects, but sadly the repo is archived and no longer maintained.

Other minimalist themes:


  • Pick a theme
  • Port current website to it

Improve site's structure

One of the problems with the current website is the structure - several documents are "misplaced". Our users have hard times finding the information they need. We also need the ability to share links with our users to precise parts of the documentation.


  • Think about a new structure and propose it to the team
  • Implement the new structure
  • Make sure a list of blog posts is well listed and browsable
  • Preserve the important links and make redirects when moving content
  • Add a way to link to specific config options

Hugo → Jekyll

GitHub has native support for Jekyll - the question is if it's worth migrating.

The biggest advantage of jekyll over hugo are plugins. Since hugo is written in go, it has all the batteries included and there is no support for plugins - do we actually care about this?

When I read about the jekyll ↔ GitHub integration, I feel like the key features are missing:

  • No preview support in PRs.
  • They suggest using travis for testing.
  • "It can take up to 20 minutes for changes to your site to publish after you push the changes to GitHub."
    • This is already solved for us by the GitHub action Jirka set up.

Raw meeting notes

* logo
* header links are not clickable - javascript copies it for you
* we have a list of posts and they are ordered randomly
* the text is too wide - a reader can get lost easily on a line
* the font is difficult to read
* likes

Franta: options in the config cannot be made links
* structure: docs for the app is disconnected from the rest of the docs

Honza: red color does not match
* we can use the colour scheme from packit logo
* letters are too thin and hard to read

Tomas likes