Open Food Facts Contents: Difference between revisions

From Open Food Facts wiki
No edit summary
Line 1: Line 1:
This page is about managing multilingual static pages.
This page is about managing multilingual static pages.


=== CMS migration project ===
== CMS migration project ==
As of today in August 2024, static pages are stored in the [https://github.com/openfoodfacts/openfoodfacts-web/tree/main openfoodfacts-web] Github repository.  Adding a new page, setting it up for translation, deploying it, is not an efficient process.
As of today in August 2024, static pages are stored in the [https://github.com/openfoodfacts/openfoodfacts-web/tree/main openfoodfacts-web] Github repository.  Adding a new page, setting it up for translation, deploying it, is not an efficient process.


Line 14: Line 14:
A first experiment to integrate the content of a WordPress page directly into the site was conclusive. ([https://github.com/openfoodfacts/openfoodfacts-server/pull/10596 PR #10596])
A first experiment to integrate the content of a WordPress page directly into the site was conclusive. ([https://github.com/openfoodfacts/openfoodfacts-server/pull/10596 PR #10596])


====How to: replace an Openfoodfacts-web page by a Wordpress page ('''Not yet in production)'''====
===How to: replace an Openfoodfacts-web page by a Wordpress page ('''Not yet in production)'''===
We plan to migrate the pages progressively. Here are the steps to follow :
We plan to migrate the pages progressively. Here are the steps to follow :



Revision as of 09:52, 22 August 2024

This page is about managing multilingual static pages.

CMS migration project

As of today in August 2024, static pages are stored in the openfoodfacts-web Github repository. Adding a new page, setting it up for translation, deploying it, is not an efficient process.

That is why, using WordPress CMS was the natural candidate (see #7983), for the following reason:

  • The UI is well known by a lot of people
  • It is already used for the blog
  • It has good support for translation and Crowdin integration

The ultimate goal is to be able to retrieve the translation of a page and incorporate it into the site/app. The challenge is also to render the page as close as possible to how it looks in the WordPress editor.

A first experiment to integrate the content of a WordPress page directly into the site was conclusive. (PR #10596)

How to: replace an Openfoodfacts-web page by a Wordpress page (Not yet in production)

We plan to migrate the pages progressively. Here are the steps to follow :

  1. Choose a page to work on. Look at openfoodfacts-web, for example: who-we-are.
  2. Go to world.openfoodfacts.org/who-we-are, to see how the page is organized.
  3. Go to the WordPress admin panel in, Pages > Add New Page.
  4. Set the title. And build the page in the editor.
    View of the WordPress Gutenberg editor on the the who-we-are page
  5. Once finished, save and publish.
  6. The title is different from the original slug who-we-are, go back to the page menu then, on the page > Quick Edit, and change it.
    View of WordPress page menu, in quick edit mode
  7. Now, if you are an admin you can go to openfoodfacts.org/content/refresh and see the page listed.
    Page menu in /content on open food facts
  8. To add a translation go to the page menu on WordPress and select the language you want to translate to.
    Page menu in WordPress showing available languages ready for translation
  9. A translation editor opens where you can edit each text.
    WPML translation editor
  10. Once finished click on "Complete Translation" at the bottom. Note that each text must be translated in order to click on that button and make the translation available.
  11. Then again refresh available pages on openfoodfacts. Now you can see the translation if go to (with our example) fr.openfoodfacts.org/content or world.openfoodfacts.org/content/fr