Proposal: splitting blog into separate site, translations go direct via merge request



The current website is difficult to have a blog in because it is hard to update frequently due to security concerns. @Coffee @NicoAlt and I have briefly discussed splitting out the blog/TWIF into a standalone site, like I think it could make a lot of sense.

The open questions that I see are:

  • what kind of site? gitlab pages? discourse? wordpress? something else?
  • how should the translations be handled? weblate? directly translated Markdown files submitted via Merge Request? something else?

@critdroid @idmpub @mesnevi @kingu


I would vote for using a static page again. However, it does not need and might should not be made using the same software as the current website (Jekyll) as we’ve noted that it not quite the best software coming to internationalization (although @hans and @uniqx are currently working on this).

Going the Python way, there’s Pelican and Lektor, with the latter soon being used by Tor and calling itself “Multilingual” (We can speak multiple languages and allow you to easily create localized websites.). Another popular option seems to be Hugo, a framework calling itself “The world’s fastest framework for building websites” and being used by at least Transportr, run by a F-Droid core member. It might also get used by Briar in future.

Whatever we choose, I would deploy it using GitLab CI/GitLab pages, given the fact that we soon have our own CI runners.



I personally think that the community readers of the blog are “geeks” who can easily read / write english texts and I would prefer that all our efforts / time go closer to “end users” by developing great softwares and providing a translated “client” quality app (the server side is also more for techies).

Best regards,


That’s not the point, translations are done by volunteers (like me) that mostly can’t just develop great software, but they can contribute translations.

Not sure why you need to bring this up, whatever framework might just need to allow for translations, it’s not like @uniqx or @hans will start to translate… :wink:


@uniqx and I looked into Lektor. It has a nice editor GUI, is written
in Python, and should support Weblate integration well. But it has a
custom file format, which is disappointing, so the existing files would
have to be converted.

Hugo has the same file format, has native localization support, and is
actively developed and widely used. It is written in Go, which is sad.
But hopefully it would just work, so we wouldn’t have to touch Go code.


Is it possible to create a gitlab project “blog-f-droid” with a project wiki where every logged-in-gitlab-user have write permission to?
This could be used as the proposed wiki.

I am using github-projekt-wikis for my github-projects for this. I do not have experiences with gitlab for this.


yup, that’s totally possible and works for me.


I’m slightly leaning towards jekyll at this point. It means we can reuse all the materials we already have, most importantly the F-Droid theme.

I looked into Hugo, and its template syntax is absolutely horrible and breaks my brain. For example, it has extremely weird ideas about case sensitivity, where variables are sort of case insensitive, but case matters, and the casing for the exact same variable needs to be different when using it in different contexts. :exploding_head:

On the up side, Hugo is Fast with a capital F.


I thought that Hugo could use the Liquid/Jinja2 templates that Jekyll
does? Or at least there seems to be an option to use Liquid with Hugo.


It does, and combines that with its own syntax for referencing page variables and such.