[opensuse-web] Static site generation for software.o.o and www.o.o
Hi, we (software.o.o maintainers) want to switch to a static site generation approach for the static parts of software.opensuse.org (distribution download pages). LCP also wants to migrate www.opensuse.org and news.opensuse.org to a static site generator, now we are looking for the right software. We have came up with two possible generators: Hugo[0] and Jekyll[1]. Before we decide which one to use, I would like to ask about experiences with either one. As far as I know kubic.o.o, openbuildservice.org and obs-patterns.netlify.com use Jekyll. Are there any issues or things that should be known before starting a project with it? Is there anyone using Hugo who could provide an answer to the same question? If there is only Jekyll in use inside the project, I think we should stick to it when we migrate the aforementioned sites. If anyone wants to help out with the migration process, please speak up so we can include you :) Best, Alex --- [0] - https://gohugo.io [1] - https://jekyllrb.com
Alexander Graul <mail@agraul.de> wrote:
Hi,
we (software.o.o maintainers) want to switch to a static site generation approach for the static parts of software.opensuse.org (distribution download pages). LCP also wants to migrate www.opensuse.org and news.opensuse.org to a static site generator, now we are looking for the right software.
We have came up with two possible generators: Hugo[0] and Jekyll[1].
Not what you asked for, but I thought I'd mention https://www.gatsbyjs.org/ in case you hadn't seen it. I don't have any experience of one vs. the other but I heard it's a pretty good option: https://medium.freecodecamp.org/gatsby-vs-hugo-a-detailed-comparison-e78d94f... If you already know about it and decided against it, feel free to ignore this ;-) -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Am 05.11.18 um 17:54 schrieb Alexander Graul:
Hi,
we (software.o.o maintainers) want to switch to a static site generation approach for the static parts of software.opensuse.org (distribution download pages). LCP also wants to migrate www.opensuse.org and news.opensuse.org to a static site generator, now we are looking for the right software.
We have came up with two possible generators: Hugo[0] and Jekyll[1]. Before we decide which one to use, I would like to ask about experiences with either one. As far as I know kubic.o.o, openbuildservice.org and obs-patterns.netlify.com use Jekyll. Are there any issues or things that should be known before starting a project with it? Is there anyone using Hugo who could provide an answer to the same question?
Be aware that none of these is translated - so take that into account early Greetings, Stephan -- Lighten up, just enjoy life, smile more, laugh more, and don't get so worked up about things. Kenneth Branagh -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
Stephan Kulow schrieb:
Am 05.11.18 um 17:54 schrieb Alexander Graul:
Hi,
we (software.o.o maintainers) want to switch to a static site generation approach for the static parts of software.opensuse.org (distribution download pages). LCP also wants to migrate www.opensuse.org and news.opensuse.org to a static site generator, now we are looking for the right software.
We have came up with two possible generators: Hugo[0] and Jekyll[1]. Before we decide which one to use, I would like to ask about experiences with either one. As far as I know kubic.o.o, openbuildservice.org and obs-patterns.netlify.com use Jekyll. Are there any issues or things that should be known before starting a project with it? Is there anyone using Hugo who could provide an answer to the same question?
Be aware that none of these is translated - so take that into account early
Let met translate that :-) A hard requirement is that the static site generator must be able to generate localized versions of the site. We use weblate for translations¹. That normally means a process as known from eg native programs using gettext. Ie the site is written in english with translatable portions tagged. Some mechanism extracts those strings and produces the input for weblate (normally po and pot files). Weblate then commits translations back into the repo (updates po files). The site generator has to pick up those translation files to generate localized versions of the english original. Site generators that are intended for eg blogs usually use a custom approach where translators more or less manually translate english articles as a whole in a one time effort. That does not work for us. cu Ludwig [1] https://l10n.opensuse.org/ -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
On 06/11/2018 19:24, Ludwig Nussel wrote:
Stephan Kulow schrieb:
Am 05.11.18 um 17:54 schrieb Alexander Graul:
Hi,
we (software.o.o maintainers) want to switch to a static site generation approach for the static parts of software.opensuse.org (distribution download pages). LCP also wants to migrate www.opensuse.org and news.opensuse.org to a static site generator, now we are looking for the right software.
We have came up with two possible generators: Hugo[0] and Jekyll[1]. Before we decide which one to use, I would like to ask about experiences with either one. As far as I know kubic.o.o, openbuildservice.org and obs-patterns.netlify.com use Jekyll. Are there any issues or things that should be known before starting a project with it? Is there anyone using Hugo who could provide an answer to the same question?
Be aware that none of these is translated - so take that into account early
Let met translate that :-) A hard requirement is that the static site generator must be able to generate localized versions of the site. We use weblate for translations¹. That normally means a process as known from eg native programs using gettext. Ie the site is written in english with translatable portions tagged. Some mechanism extracts those strings and produces the input for weblate (normally po and pot files). Weblate then commits translations back into the repo (updates po files). The site generator has to pick up those translation files to generate localized versions of the english original.
Site generators that are intended for eg blogs usually use a custom approach where translators more or less manually translate english articles as a whole in a one time effort. That does not work for us.
cu Ludwig
Yep this is the exact reason its not already done, there was plans well in progress for a move to Jekyll several years back, but these were abandoned due to lack of translation support. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
On 11/6/18 9:54 AM, Ludwig Nussel wrote:
Stephan Kulow schrieb:
Am 05.11.18 um 17:54 schrieb Alexander Graul:
Hi,
we (software.o.o maintainers) want to switch to a static site generation approach for the static parts of software.opensuse.org (distribution download pages). LCP also wants to migrate www.opensuse.org and news.opensuse.org to a static site generator, now we are looking for the right software.
We have came up with two possible generators: Hugo[0] and Jekyll[1]. Before we decide which one to use, I would like to ask about experiences with either one. As far as I know kubic.o.o, openbuildservice.org and obs-patterns.netlify.com use Jekyll. Are there any issues or things that should be known before starting a project with it? Is there anyone using Hugo who could provide an answer to the same question?
Be aware that none of these is translated - so take that into account early
Let met translate that :-) A hard requirement is that the static site generator must be able to generate localized versions of the site. We use weblate for translations¹. That normally means a process as known from eg native programs using gettext. Ie the site is written in english with translatable portions tagged. Some mechanism extracts those strings and produces the input for weblate (normally po and pot files). Weblate then commits translations back into the repo (updates po files). The site generator has to pick up those translation files to generate localized versions of the english original.
With Jekyll I think we could manage that. F-Droid is using Weblate and Jekyll for their website, so it is at least possible to do :) Maybe we can adapt their way [0] of doing it for our purposes. [0] - https://gitlab.com/fdroid/fdroid-website/blob/master/_docs/Release_Process.m...
Alexander Graul schrieb:
On 11/6/18 9:54 AM, Ludwig Nussel wrote:
Stephan Kulow schrieb:
Am 05.11.18 um 17:54 schrieb Alexander Graul:
we (software.o.o maintainers) want to switch to a static site generation approach for the static parts of software.opensuse.org (distribution download pages). LCP also wants to migrate www.opensuse.org and news.opensuse.org to a static site generator, now we are looking for the right software.
We have came up with two possible generators: Hugo[0] and Jekyll[1]. Before we decide which one to use, I would like to ask about experiences with either one. As far as I know kubic.o.o, openbuildservice.org and obs-patterns.netlify.com use Jekyll. Are there any issues or things that should be known before starting a project with it? Is there anyone using Hugo who could provide an answer to the same question?
Be aware that none of these is translated - so take that into account early
Let met translate that :-) A hard requirement is that the static site generator must be able to generate localized versions of the site. We use weblate for translations¹. That normally means a process as known from eg native programs using gettext. Ie the site is written in english with translatable portions tagged. Some mechanism extracts those strings and produces the input for weblate (normally po and pot files). Weblate then commits translations back into the repo (updates po files). The site generator has to pick up those translation files to generate localized versions of the english original.
With Jekyll I think we could manage that. F-Droid is using Weblate and Jekyll for their website, so it is at least possible to do :) Maybe we can adapt their way [0] of doing it for our purposes.
[0] - https://gitlab.com/fdroid/fdroid-website/blob/master/_docs/Release_Process.m...
The translation process is explained at https://gitlab.com/fdroid/fdroid-website/blob/master/TRANSLATIONS.md So looks like there are two methods. One method for posts where markdown is converted back and forth to/from po. Another method for fixed strings in the website. The former is kind of ok IMO, even though very basic as it includes e.g links in the string for the translator instead of a placeholder. That requires more knowledge on the side of the translators. The second method looks antiquated and cumbersome. Gettext doesn't need intermediate dictionaries with keys to reference strings. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-web+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-web+owner@opensuse.org
participants (5)
-
Adam Spiers -
Alexander Graul -
Ludwig Nussel -
Simon Lees -
Stephan Kulow