Skip to main content

New best story on Hacker News: Show HN: An open-source collaborative WYSIWYG Markdown editor

Show HN: An open-source, collaborative, WYSIWYG Markdown editor
443 by arek_nawo | 127 comments on Hacker News.
Inspired by the design and UI/UX of apps like Notion, and utility of open-source apps like StackEdit, I decided to create a minimalistic, local-only WYSIWYG Markdown editor. Some features worth highlighting: - Monaco editor and Prettier integration for code snippets - Tables (apparently the holy grail of WYSIWYG editing) - Embeds (for CodePen, CodeSandbox and YouTube, most useful for HTML or JSON exports) - Accepts Markdown paste-in, and "exports"/generates HTML, Markdown and JSON outputs - Collaboration (with real-time awareness and initial commenting system, available only when logged in) - GPT-3.5 integration (only when logged-in with the corresponding extension installed) Stack used: TipTap, Solid.js, HocusPocus, Fastify, tRPC. Some notable drawbacks: - No mobile support - Collaboration available only between signed-in users, in the same workspace; - I tried my best to support most common Markdown formatting, pasting and in-editor shortcuts, though there might still be room for improvement - Self-hosting isn't easy right now, though you should be able to figure it out from the source code The editor itself is a standalone app, extracted from the larger Vrite CMS project ( https://ift.tt/6rILCWN ) which you can also test out (only with sign-in) here: https://app.vrite.io/

Comments

Popular posts from this blog

New best story on Hacker News: Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates

Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates 449 by SimingtonFCC | 144 comments on Hacker News. Hi everyone, I’m FCC Commissioner Nathan Simington, and I’m here to discuss security updates for IoT devices and how you can make a difference by filing comments with the FCC. As you know, serious vulnerabilities are common in IoT, and it often takes too long for these to be patched on end-user devices—if the manufacturer even bothers to release an update, and if the device was even designed to receive them. Companies may cease supporting a device well before consumers have stopped using it. The support period is often not communicated at the time of sale. And sometimes the end of support is not even announced, leaving even informed users unsure whether their devices are still safe. I’ve advocated for the FCC to require device manufacturers to support their devices with security updates for a reasonable amount of time [1]. I can't bring such a proposal