Currently the docs are only written in English and the docs folder structure is setup for only one language. A first nice step to ease the creation of a translated version is to create a /en/ folder with the exisiting docs and update the links.

If you're not sold on the idea of denoting the main language (english) with a new route it can be left as is and have the translations placed inside s

Because of warning with some Hoc (acdlite/recompose#795) we have te remove recompose and replace it with Hooks.

Issue: If nested routes are used, Passage will not have access to all of the routes at any given point in time.

How can Nested Routes be used with Passage? Is this possible?

For better real-life usage, react-formular should be integratable into some popular ui frameworks like Material or grommet.

I was thinking about a sub package with some naming convention like react-formular-{uiFramework}.

Need to update the readme.md to reflect the changes in the most recent pull request.

• Context.Provider and Context.Consumer have been destructured for ease of use and are now imported as Provider and Consumer
• All Components were changed to Functions to support the use of hooks
• Actions and store work the same, but we changed the way appContext.js works
  • instead of class componen