Guidance on third-party extensions and BlockNote’s extension ecosystem

[gsingh-ds]

First of all, we at DefenseStation really appreciate the BlockNote project and the work the team has done.

We have been using BlockNote since around version 0.15, possibly even earlier. Over time, we have built several extensions for features we needed, and we also maintain the Awesome BlockNote repository.

More recently, we have worked on extensions for features such as superscript and subscript, math support, comments, and export functionality. We built some of our own export tools before BlockNote introduced its commercial PDF and HTML export features.

We want to make sure our work supports the BlockNote ecosystem without conflicting with the project’s commercial plans. We understand the importance of those commercial goals, and we are open to supporting them in the future.

We would appreciate some guidance on a few questions:

1. Are there any boundaries or guidelines for third-party extensions?
2. How does the team decide which features belong in the core editor, which should be official extensions, and which are suitable for community extensions?
3. Is it reasonable for us to continue investing time in building and maintaining extensions for features that may already be on the BlockNote roadmap?
4. Would the team prefer these extensions to remain in our own repositories, or would contributions to the BlockNote organization or project be welcome?
5. Are there any types of extensions, particularly around commercial features, that community developers should avoid publishing?

Our goal is to contribute positively to the ecosystem and avoid duplicating work in a way that creates confusion or conflicts with the project’s direction.

Any guidance on how the BlockNote team sees the future of third-party extensions would be very helpful. Thank you again for all the work you are doing on the project.
@YousefED