docs: unify documentation

[magicmatatjahu]

Description

Changes proposed in this pull request:

• Update main Readme.md
• Update License and authors
• Move instruction of using web-component to ./docs/usage/web-component.md document.
• Move instruction of using web-component in Angular to ./docs/usage/angular.md document.
• Describe how to use the component in NextJS app in ./docs/usage/nextjs.md document.
• Mention about esm, cjs and umd modules.

Related issue(s)
Part of asyncapi/shape-up-process#83

[derberg]

looking on the change, IMHO we should release it as 1.0.0-rc.1

there are breaking changes that will cause issues to users if they just automatically bump. Component is changing a lot and we should clearly indicate that. This will also enable us to ship something that is not final and get feedback from current users.

We also need a migration guide, a short list of things that users need to do to switch to this release candidate. Best if it is published under the releasae

[magicmatatjahu]

@derberg Thanks for review!

looking on the change, IMHO we should release it as 1.0.0-rc.1

there are breaking changes that will cause issues to users if they just automatically bump. Component is changing a lot and we should clearly indicate that. This will also enable us to ship something that is not final and get feedback from current users.

I don't agree with this 1.0.0-rc.1. It should be released as 0.24.0 (with 0.23.0 where we fix all security issues in old version). Maybe the component has changed a lot, mainly the styling, but I don't think that's a reason to start with 1.0.0 (even rc). We still have 0.X.X so users should be prepared for breaking change.

We also need a migration guide, a short list of things that users need to do...

Sure :) I will remember about that.

@fmvilas What do you think about release?

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[derberg]

I approve. Topic of release is not blocking for this PR imho. Just open another issue or simply make a note that in a final PR we need to discuss the release type and migration guide

[magicmatatjahu]

@derberg Thanks! I will add note in final PR.

[asyncapi-bot]

🎉 This PR is included in version 0.21.0-next.1 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀