On Booster 1.0.0 - New build tool and documentation overhaul

[NickSeagull]

Hey everyone!

Since the beginning of the project, Booster has gone through a lot of changes, bugfixes, new features and magic. Right now it is in a point where it is running in production systems flawlessly with no hiccups.

Of course, software is not perfect, and all programs will have bugs, but we're pretty confident to say that Booster and it's API are pretty stable and ready to be called 1.0.0!

Although the preparations for 1.0.0 are halfway there, here is what has been happening and what comes next:

• We're ditching Lerna as our build tool in favor of Rush. Lerna has served us well up to this point, but we've found it inconsitent in the build process as well as slow. Some of the users and contributors already started to use Yarn as a replacement for Lerna, but the core team decided to go with Rush because we've found it much faster than the rest of the tools, plus it is optimized for managing monorepos in large organizations.
• With this, contributors need to change their contribution flow, and although it is only using about Rush instead of Lerna, this needs to be documented properly so we're all on the same page.
• Given that we need to change quite a bit chunk of the contributing docs, we've decided that it is a great moment to overhaul our documentation page and switch from our custom solution to a proper tool like Docusaurus.
• Along with this, we will integrate API Extractor to ensure that changes do not break the API of the framework and it is consistent to the versioning schema we're following (semantic versioning).

The idea is that this sets up some foundation for better collaboration in the project, as well easier learning for newcomers! This enable to work in the future on things like:

• Automatic dependency bumping
• Better contributor developer experience
• Interactive examples in the docs
• And much more

Looking forward to read your opinions!

[NickSeagull]

Booster 1.0.0 was already released, closing