Re: Ideas for gnome.org

[Tom Tryfonidis <tomtryf gmail com>]

On 6 September 2016 at 00:02, Allan Day <allanpday gmail com> wrote

That could be an issue indeed, although it is already the case for some parts of gnome.org (you need to use git to change the screenshot on the home page, for example).

Other things we'd need to think about:

• Search (is it needed for a minimal site? Would we want a global GNOME search that would bring in results from different GNOME sites (yes please!)?

• Translations - we haven't got them working for the current website - how much work would it be to get them working? Would it be easier for a different setup?

• Integration with the blog, through RSS or similar.

• Integration with Friends of GNOME/Paypal.

And so on.

An update about the translations.

I tested WPPO [1], the plugin we previously used on gnome.org, and it works with minor fixes.

- Theme's translation works out of the box, we need to mark the pages as translatable, translate them and put the *.mo files under this directory [2].

If we decide to stay with WordPress, it would be good to move the pages without frequent changes of content (e.g. About Us, Merchandise, Get Involved etc.) to git, as we do with Homepage (page-home), FoG (page-friends) etc. (I'll explain it below)

- Content translations (static and dynamic) depend on WPPO, which pulls the translations from WordPress posts (dynamic content) and pages created from the WP admin panel (static content - About Us, Merchandise ...). I've experienced encoding problems with these type of translations, because itstools complains about the tags.

For instance, static content translations break if i translate this line:

Select one of these Amazon Stores: <_:a-1/>  <_:a-2/> <_:a-3/> <_:a-4/> <_:a-5/> <_:a-6/>

(same happens in dynamic content when i have a sequence of tags  <_:a-1/>  <_:a-2/> ... <_:a-n/>)

throwing this error:

'ascii' codec can't encode characters in position 0-6: ordinal not in range(128)

In my opinion, we need to set our goals about the translation.

Do we need a fully translated website, including dynamic content (mostly news posts); or

a website with its main places tranlated (navigation menus, footer, static pages)?

Tom

[1] https://wiki.gnome.org/GnomeWeb/WPPO
[2] https://git.gnome.org/browse/gnome-web-www/tree/theme/languages