At its core, React apps in Webiny are very similar to those created by create-react-app tool. However, to make things work exactly the way we wanted them to, we had to think differently about how we approach app structure and file organization. We want to be able to share apps, not React components. We also want to have the minimum possible amount of boilerplate code, and still keep the ability to customize both app's logic and structure, as well as the bundling process.
As you may already know, with Webiny, everything is a plugin. React apps are no different. Routes, menus, views - everything is added to the app by registering new plugins.
With traditional React apps, you would import all your components and mount them in a very declarative and static way. To add new things to your app, you would have to import a particular component, and mount it somewhere. With Webiny, you can finally compose your apps using plugins. This gives you the freedom of using community plugins, and even creating entire app templates, and sharing them as simple
How does it work in practice?
Check out our knowledge-sharing session on
APP Development With Webiny. We'll get to know the structure of the app, how it is bundled, and how to make reusable app templates.
Bootstrapping an app is as simple as importing an app template package (which is essentially a React component factory), and executing it with the supported options to get your app component:
And there you have your fully featured Webiny Admin app! Pretty cool, isn't it? In the following articles we'll dive deeper into the anatomy of an app template and how plugins make all of this possible.
But first, we need to learn how to setup a new React app within your Webiny project.