Enhanced documentation

[Jonghakseo]

Is your feature request related to a problem? Please describe.

As reported in several issues, creating the extension itself, and using this boilerplate in the process, requires more explanation.

Describe the solution you'd like

More detailed and improved documentation is needed. We are thinking of documentation based on each package's README.md, but it may be necessary to provide a self-hosted documentation page.

Describe alternatives you've considered

I think we can share information in the Discord community before documenting it.

Additional context
Add any other context or screenshots about the feature request here.

[PatrykKuniczak]

Basing on that comment: #651 (comment)

I think good idea is to add tutorials to the most popular lib, as MUI/Chakra UI/Radix and so on to new DOCS as we have on the legacy version

[Jonghakseo]

@PatrykKuniczak

I agree. I want to turn Markdown files in this repository into a webpage as it is.

https://github.com/wranders/markdown-to-pages-action

I'm looking at something like the project above.

[PatrykKuniczak]

@PatrykKuniczak

I agree. I want to turn Markdown files in this repository into a webpage as it is.

https://github.com/wranders/markdown-to-pages-action

I'm looking at something like the project above.

I haven't heard about it in the past, that's interesting, because we don't need any new hosting, github pages are free 😁

[dandv]

I've improved the README a bit but I agree that the documentation assumes users know how Chrome extensions work. Maybe it's better that way, to avoid everyone and their dog from publishing half-baked extensions.