Date: prev next · Thread: first prev next last
2021 Archives by date, by thread · List index


On 3.9.2021 21.11, Yaron Shahrabani wrote:
On Fri, Sep 3, 2021 at 5:53 PM Ilmari Lauhakangas <
ilmari.lauhakangas@libreoffice.org> wrote:

Hello,

as some of you may know, a small but growing team has been working on a
completely new website over the past months, and we're making good
progress!

Apart from a new and fresh design, that will finally also properly
support mobile phones and tablets, we've spent quite some time on the
backend system and shared various bits of information with you on this
already.

We've decided to go with the Hugo static site generator, storing the
content in Markdown files and tracking changes in Git. There is no
longer a need to request permission for editing the content or the site
structure and localisation can happen in Weblate.

As the website should be for you, our Community, we're eager to hear
your feedback on the editing process of the proposed new website and
we've decided to provide another testing facility! Master choreographer
Guilhem whipped up an infrastructural dance routine, which makes it
possible to preview changes to the website online. Please do give it a
try and share your questions and feedback with us:
- here on the mailing list
- privately to ilmari.lauhakangas@libreoffice.org
- on the #tdf-infra chat channel
https://wiki.documentfoundation.org/Website/IRC#Channels

We'd like to encourage especially the localisers who need unique pages
to try things out.

Editing the website comes in three easy steps:

1. Edit the website in Gerrit as in the recorded demonstration:
https://www.ilmarilauhakangas.fi/gerrit_website_demo.mkv
2. Wait 5 minutes
3. Visit https://newdesign2.libreoffice.org/changes/1234 where 1234 is
your Gerrit change number

All kinds of nonsensical changes are welcome - just write the commit
message in a way that it is clear you are testing.

Don't hesitate to reach out for any questions you may have!

Ilmari

> Hi, I've looked at the video and I want to see if I could add RTL support
> for Hebrew, Arabic, Persian, etc. the only thing I need to find is a way to
> determine these languages are selected so that the right CSS will be
> applied.

Ok, I've added this logic to the html element attributes: lang="{{ .Site.Language.Lang }}" dir="{{ .Site.Language.LanguageDirection | default "ltr" }}"

...as well as commented out direction specifications in the config.toml. Commented out, because the site will not build if the languages are defined, but their content does not exist.

As we are still in the feedback phase, the exact localisation and content structuring strategy has not been decided. I would expect us to use separate directories for localised content as in https://gohugo.io/content-management/multilingual/#translation-by-content-directory

Ilmari

--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.