Users can navigate and use OFN features in their own visual environment

What is the need / problem

Some users, especially big ones, want to use OFN features but in their own independent (standalone) website, with their own brand, design and user journey. They want to stay connected with the global network, so they don’t want to make their own deployment, they want to be able to use a public already deployed OFN instance but access features in their own environment.

Who does it impact

Lots of users.

What is the current impact of this problem

Limit adoption of the OFN.

What is the benefit in focusing on this

Increase the user base.

Links to more details

Potential solutions that will solve this problem

  • First feature candidate already implemented: embed shopfront / embed group, but it limits use of OFN features to only those two features in an external environment.
  • Enforce a powerful API could be a second iteration.
1 Like

@MyriamBoure can you please assign this icebox item a sub-category? Draft or Review Ready or Approved?

There has actually been a lot of talking and work done that relates to this item…do we need to revise this, and also consider it in light of potential new business models (e.g. charging for anything beyond the freemium current embedded shop feature). What do you think?

This is way too big to be able to prioritize, back to curation, the first thing to prioritize before going anywhere here is document our API which can be prioritized already…

Moved to Users can navigate and use OFN features in their own visual environment · Issue #81 · openfoodfoundation/wishlist · GitHub Closing