What is a preset?

Presets are opt-in, meaning that you, as a developer, get to choose which one to use. This decision is up to you only, and you will likely remove some of built-in feature to match your business needs/requirements.

Why presets?

The boilerplate was built with re-usability in mind, but also tries to solve non-trivial issues such as:

• Analytics Not released yet
• Monitoring Not released yet
• Static i18n Not released yet
• API Handling

Those are non-trivial features, and they can’t always be build using open-source software.

They are non-trivial to build from scratch, and the use of established standards and worldwide known vendors sometimes helps a lot.

Presets are meant to provide various possibilities of recommended “base code”. For instance, you may want to use:

• Sentry to monitor your app (client + server sides), but maybe you already use another different vendor and would like to stick with it
• Analytics, but because your needs are small then Google Analytics may be a better fit
• Etc.

This architecture currently covers quite a few features, and relies on 3rd party vendors for some of those features.****

Limitations

We don’t intend of supporting all possible variations though, but we’ll try to focus on the basic ones, and most requested ones.

The more presets we will offer, and the easiest it will be for any newcomer to get started quickly with a preset that matches their needs as closely as possible, although at the price of ease of maintenance of those multiple presets.

Which presets are being considered?

Here is a short list of all presets that we consider to support in the future: