[Help Wanted] We're planning to open-source the OpenMarkdown editor as an npm package
by•
We're planning to split the editor inside OpenMarkdown out as an open-source (MIT) npm package that anyone can drop into their own app. The app itself stays as it is.
Before we do, we'd love to hear from you:
1. If you build apps: what would make you actually pick an open-source editor component over the one you use now? Tests? Docs? A live demo? How fast issues get answered? AI/Agent friendly docs?
2. If you use OpenMarkdown: does the editor being open source change how much you trust the app — or do you not care as long as it works?
3. Open editor, closed app: does that split feel fair to you, or does it read as "open source as marketing"?
Honest answers, including "nobody needs another editor", are the most useful.
19 views


Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.