You should put what the requirements are up-front. Only after reading through the file-structure did I understand that your plugin assumes both React and TypeScript is being used for building the extension.
It'd be great if the documentation could start with showing how is different from the many other similar solutions that came before you, to make users understand the value proposition of your framework a bit better.
I went to the main-page to see what the main product you were building, and seems the browser extension framework is the main product. I'm not sure if the Pricing is placeholder pricing or not, but $256 per user per month sounds like a lot for a extension framework, but maybe I'm not the target audience, I've only published a few browser extensions as an individual.
It is indeed placeholder pricing - I am not entirely sure how to structure this business yet, really wanted to lean toward an open-source model with premium support (hence the 256 pricing tag on premium support).
The framework itself is free. Only if the user require hands-on contracting work (i.e, a demo of integrating with their in-house framework) would it trigger the support price.
Your feedback indicates I should separate the "enterprise-support" pricing from the "Developer" or Team pricing, and also make it less expensive (certainly lower than $256). Since the base framework is free (like Next.JS), how much would you as a solo developer pay for a feature that allows you to test your extension without having to submit and wait for the chrome/edge webstore review?
It'd be great if the documentation could start with showing how is different from the many other similar solutions that came before you, to make users understand the value proposition of your framework a bit better.
I went to the main-page to see what the main product you were building, and seems the browser extension framework is the main product. I'm not sure if the Pricing is placeholder pricing or not, but $256 per user per month sounds like a lot for a extension framework, but maybe I'm not the target audience, I've only published a few browser extensions as an individual.