If the localized content of the new website is is to be inputed via
Weblate and I don't have to go anyware near the technical side of the
site than no probs. This is the situation with Mozilla, I translate in
pontoon and the content appears on the various website within a short time.
My concern is the suggestion that locales could create their own
content. However, im my view the level of technical competency within
some locale groups may stop them from being able to do so. This would be
a loss to the whole LibreOffice community.
I'm sorry, but I'm doubtful if I would be able to contribute under this
Ar 08/09/2021 07:50, ysgrifennodd Ilmari Lauhakangas:
On 7.9.2021 12.40, Andreas Mantke wrote:
Am 06.09.21 um 18:52 schrieb Brett Cornwall:
On 2021-09-06 15:18, Rhoslyn Prys wrote:
Hmmm, that looks pretty technical to me...
Any chance of doing something nice and easy in WordPress or similar?
Just asking :-)
I cannot speak for those owning this project.
Hugo is most certainly a much simpler solution from a maintenance
perspective. Wordpress (and similar CMSes) is a nightmare to maintain
and always devolves into a mess of plugins (that everyone is too
afraid to change/deactivate for fear of breaking the site), custom PHP
snippets galore, horrible WYSIWYG battles, and a general feeling of
dread for ever updating/changing Wordpress. So long as reliance on
libreoffice.org's maintainability and performance (and likely SEO).
As for Git, this technical barrier is a downside for those unfamiliar:
Those in charge of content may very well not be comfortable with Git.
I should hope that the owners of this project solicited feedback from
those in charge of the site content. It's important that they are
comfortable with such a workflow.
If it weren't for merge conflicts and other VCS-isms I would argue
that learning simple markdown files + a Git GUI would be miles simpler
that learning how to use Wordpress... :)
and for those who think content contributors had only to learn markdown
and Git to make valuable contributions have no clue about non-tech-savvy
First: it's not more easy to learn markdown + Git than to use a CMS for
a content contributor (most of them are usable like an office text
Just like with GitHub's direct editing functionality, you don't need
to actually understand Git in order to make contributions.
To put things into perspective, in my site restructuring plan, there
are only about 15 separate pages on libreoffice.org. Besides the very
small number of pages, the structure and even the content will remain
fairly static, so a CMS would be overkill.
Second: if you want to get a look onto your changes / contributions
before you submit them you need a local build environment. It works not
out of the box with a current Debian 11 fresh setup.
This is true because I use a feature introduced in Hugo 0.82 while
Debian 11 ships 0.80. However, Go programs like Hugo are distributed
as single binaries, so you can just download any recent release and
In the case of Linux you could grab
I did not go into these details, because the focus of this feedback
phase is direct editing in Gerrit.
07815067805 / 01248 351289
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/website/
Re: [libreoffice-website] Re: Our new website is progressing - have a look! · Ilmari Lauhakangas
- Re: [libreoffice-website] Our new website is progressing - have a look! (continued)
- Re: [libreoffice-website] Re: Our new website is progressing - have a look! · Rhoslyn Prys
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy