Hacker News new | past | comments | ask | show | jobs | submit login

Structured editors are cool. Not everything needs to be org-mode, but I feel like this project could learn from some existing tools:

• Quip's block level editing (https://quip.com/). This avoids the problem where users can't decide whether they should make multiple paragraphs within a block, or if they should make multiple blocks with one paragraph each — Quip makes it so that pressing return puts you into a state where you've created a whole new block-level chunk of information. Whether that's a paragraph or a heading or an image or a table, it doesn't matter because it enforces that the space must mean something. It even prevents you from pressing return multiple times, which would be handled in other wysiwyg editors with multiple <br>s or javascript margins or god knows what else.

• The ability to track and apply revisions a la substance.io (http://substance.io/#substance/manual). Having granular control about both the contents and placement of blocks is very important, especially when considering that a lot of content is edited while being written and revised once published. Substance's extension API is worth checking out too.

That said though, I think you're doing great work, and I'll be watching this project closely. Death to TinyMCE!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: