- Please ask assignment before starting to code. First asking, first assigned. We have enough issues for everyone. Please open a matching issue and get consensus before raising PRs.
- DO NOT create a bug and its PR at the same time. Create the issue first and ask to be assigned.
- Do not try to race other contributors to solving an issue. Try something else, or try collaborating or helping one another on solving it.
- DO NOT jump to implement an open issue before an agreement is reached on the design.
- LINT your PRs before sending them pnpm
- Please mention GenAI tool you used if you used it (Copilot in an IDE, Copilot Workspace, Gemini…)
- openfoodfacts-explorer is our experimental, next gen frontend. The idea is to reach feature parity on the essential stuff with the main frontend to eventually replace it, with a much better responsive UI (80%+ of our traffic is mobile web).
- We currently don’t have any real visual mockup of it, nor “artistic direction” so for the time being, we're copying key features from the current frontend, improving them whenever we can.
Mockups on the current website
Trying to create a digital twin of openfoodfacts-explorer
- Are you a designer ? Join the design team
- Uses the official Open Food Facts NodeJS SDK
- Basic editing
- Product page display, including Knowledge Panels support
- Search
- Login support (simple login)
- Folksonomy Engine Support
- Using more openfoodfacts-nodejs
- Using more openfoodfacts-webcomponents
- Image editing and image upload
- Product Addition
- Support for Open Prices
- Support for Search-A-Licious (including facets)
- Support for Nutri-Patrol
- Support for static content (eg /discover, /contribute…)
- You can also join the #off-explorer channel on the Open Food Facts Slack: https://slack.openfoodfacts.org
- We e-meet Wednesdays · 11:00 – 11:25am - Time zone: Europe/Paris
Video call link: https://meet.google.com/uep-fhvf-gto
- Join by phone: https://tel.meet/uep-fhvf-gto?pin=8160344286211
- Add the Event to your Calendar by adding the Open Food Facts community calendar to your calendar
- Weekly Agenda: please add the Agenda items as early as you can. Make sure to check the Agenda items in advance of the meeting, so that we have the most informed discussions possible, leading to argumented decisions.
- The meeting will handle Agenda items first, and if time permits, collaborative bug triage.
- We strive to timebox the core of the meeting (decision making) to 30 minutes, with an optional free discussion/live debugging afterwards.
- We take comprehensive notes in the Weekly Agenda of agenda item discussions and of decisions taken.
This project uses pnpm. If you have corepack enabled, you should be able to directly use pnpm
commands. Otherwise, you can install pnpm with npm install -g pnpm
.
First, install dependencies:
pnpm install
Before running the project, set up the environment variables:
cp .env.example .env
Edit the .env
file as needed to configure your development environment.
Then start the development server:
pnpm run dev
# or start the server and open the app in a new browser tab
pnpm run dev -- --open
To create a production version of your app:
pnpm run build
You can preview the production build with pnpm run preview
.