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
kept to a minimum, this will be a win for 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... :)
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/website/
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