• Writing a knowledge panel about a topic
• Updating a static page
• Reviewing and merging translations PRs on this repository
• Volunteering on the CMS project to replace this very manual process.

• We strive to thoughfully design every content page before we move on to implementation, so that we respect Open Food Facts' graphic charter and nascent design system, while having efficient user flows.
• Mockups on the current app and future plans to discuss
• Note that @manoncorneille and @galnaf have proposed a revamp for the Discover and Contribute pages
• Note that we have a detailed mockup for the landing page that hasn't been implemented (and would be high value)

https://crowdin.com/project/openfoodfacts

• Create a pull request on openfoodfacts-web with the new or modified HTML file (you can do that with the "GitHub Desktop" app if you are unfamiliar with the command line)
• Set it up for translation in the .crowdin file
• Once the pull request gets approved and merged, it will be deployed on the test server
• Deployment to production is still manual

• Do not hotlink ressources like images, JS or CSS. They need to be commited to the repository. Please organize resources in folders.

1. Move the /lang dir from openfoodfacts-server to openfoodfacts-resources (or maybe to make things even cleaner, to a new repo openfoodfacts-web. It's unclear if everything in openfoodfacts-resources is supposed to be available as-is on the web server).

2. Create a /html/images/texts/ directory in openfoodfacts-web so that we can put the new images needed by texts there (we don't have to move the existing ones right away).

That way for deployment, we can just copy /lang and /html to /srv/off/ and it will work.

See openfoodfacts-server:docs/how-to-guides/using-pages-from-openfoodfacts-web.md

And that's it! That would be already be enough of a big change for a first step. Then we can have a look at what we have in /html/ to see what we should move, one by one.

• Basic command generator