plasmo VS docs

Ooof!! It is an... interesting time right now in extensions land. The switch from MV2 to MV3 is a bit chaotic but hopefully tools like this (Bedframe) and tools like [Plasmo](https://github.com/PlasmoHQ/plasmo) start to inject some freshness in the space.

GitHub: https://github.com/PlasmoHQ/plasmo

Shameless plug, but we built the Plasmo Framework to make that (and a lot more) super easy: https://github.com/plasmohq/plasmo

Thanks! We wrote a custom Parcel runtime [1] inspired by Parcel's HMR runtime (which was too bloated and buggy for us) that injects a web socket listener into the development build of the extension.

Whenever a bundle change happens, Parcel sends it the refresh message and it either does `chrome.runtime.reload()` or `location.reload()` depending on the context.

[1]: https://github.com/PlasmoHQ/plasmo/blob/main/packages/parcel...

Plasmo: A framework for building Chrome extensions.

Check out https://docs.plasmo.com/

- We have remote code bundling that automatically fetches URL based imports (like Google Analytics) in build time to mitigate issues with MV3 not allowing remote code [4]

[1]: https://docs.plasmo.com/#where-is-the-manifestjson-file

[2]: https://docs.plasmo.com/workflows/env

[3]: https://github.com/PlasmoHQ/examples/tree/57791e70549441e391...

[4]: https://docs.plasmo.com/workflows/remote-code

We decided to tackle this problem by building a framework for browser extension development called Plasmo. It's a different way of thinking about browser extensions, and if you're used to building extensions, some things might look a bit weird.

Would love to get people to try it out and get feedback. Right now, we're focusing only on supporting React so that we can iron out all of the different edge cases that might arise, but will look to add other view frameworks like Svelte, Vue, etc. in the future! Here are the docs: https://docs.plasmo.com

Fixed - it should point to the https://github.com/PlasmoHQ/docs instead