Hashnode’s new editor went live this week and the design choice that stands out is what they didn’t port from Notion. There’s no toggle list. No callout. No basic table. What you do get: a code block with per-language LSP-grade syntax highlighting, an inline diff block, a runnable embedded snippet (currently JS/Python), a terminal-output block, and a “callout” block that’s specifically for warnings and gotchas, not for marketing-flavored asides.
The form follows the audience: technical bloggers don’t need a project tracker disguised as a doc tool; they need first-class code primitives. Type system is good: Sohne for body, JetBrains Mono for code, no quotation marks getting smart-curled inside code blocks. What’s not landing: the slash-menu is too deep (3 nested categories before you reach “code block”), and the editor occasionally drops cursor focus when you tab out of an inline code span. Both are first-week-of-shipping bugs, not architectural ones. Pattern to steal: if you’re building a block editor for any specialist audience, audit your block list against your users’ real artifacts. If you’re shipping the same 16 blocks Notion has, you’re building Notion. Cut hard.