🎯 What can i work on ? (open-prices)

[teolemon]

What

Tasks

Beta Give feedback

1. Code improvements (tooling, async...) #31
   ⭐ top issue 🏄‍♀️ good first issue +2
2. Create a Location model #13
   📍 Location +1
3. Create a Product model #12
   +0
4. Endpoint to get a proofs' prices #160
   Proofs ✅ Task +2
5. Tutorials to help contributors #158
   ✅ Task 📚 Documentation +2
6. Make the Landing page translatable

Make input easier

Beta Give feedback

1. Detect barcodes in proofs

Make interesting and thought provoking visualization

Beta Give feedback

1. Store & sync the product categories from OFF #154
   Categories Product data sync ✅ Task +3

Create a road to refresh/complete product data

Beta Give feedback

No tasks being tracked yet.

Deploy Open Price Everywhere

Beta Give feedback

1. Request: Scan product name from store price labels smooth-app#4588
   Product addition ✏️ Editing - Basic info input ✨ enhancement 🎯 P1 +4
2. Official Open Food Facts mobile app
3. Open Food Facts website
4. 3rd party apps

Elsewhere

• Adding support for the Prices project openfoodfacts-dart#831

[Apurv428]

@teolemon I'm eager to contribute to the translation of the landing page. To proceed, could you please specify the target language for the translation?

[dq18]

Thanks @Apurv428 for your help ! In any language you feel confident translating to.
The landing page is here:
Landing page
And tutorials on contributing to add prices are here (would be great to have users from everwhere!):
tutorials
Also the frontend has a collaborative translation system with Crowdin:
Crowdin
Register, go to the language you want to translate, then choose the open-prices-frontend folder:

[raphodn]

@Apurv428 if you're talking about the project landing page, I created an issue to help you out ! #184

[Apurv428]

Thank you for y'll assistance. I'll begin working on it and submit a pull request as soon as I can.

[Apurv428]

Can we make the translation of the landing page by using libraries or Google Translate? This way, we can cover various languages that users might use.
Instead of creating separate folders, like it's done in this PR, can we explore the above approach?
@dq18 @raphodn

[raphodn]

@Apurv428 can we continue the discussion in the corresponding issue ? thanks ! #184