Open Food Facts Contents: Difference between revisions
Antoineb456 (talk | contribs) (created the page) |
Antoineb456 (talk | contribs) 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 === | ||
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. | |||
That is why, as described by the issue [https://github.com/openfoodfacts/openfoodfacts-server/issues/7983 #7983], using WordPress CMS was the natural candidate, for the following reason: | |||
* The UI is well known by a lot of people | |||
* Is already used for the [[Blog planning|blog]] | |||
* It has good support for translation and Crowdin integration | |||
The ultimate goal is to be able to retrieve the translation of a page, just its content, 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. ([https://github.com/openfoodfacts/openfoodfacts-server/pull/10596 PR #10596]) | |||
Revision as of 14:48, 21 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, as described by the issue #7983, using WordPress CMS was the natural candidate, for the following reason:
- The UI is well known by a lot of people
- 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, just its content, 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)