All activity
The Big Idea
MDX changed the game for documentation, but it has a massive Achilles' heel: Security. Because MDX allows arbitrary JavaScript and import statements, you can’t safely let untrusted users author content.
Enter RDX.
RDX is a strictly typed, declarative document format built as a superset of CommonMark. It gives you the power of rich, interactive components () with the security of a pure data format. No eval(), no JavaScript runtime, and zero risk of XSS.
RDXReactive Document eXpressions: Components as Data, not Code.
Farhan Syahstarted a discussion
RDX: Is "Docs as Data" the future over MDX?
Hey everyone, I’ve been playing around with RDX (Reactive Document eXpressions) recently and wanted to see what the community thinks about it. For context: MDX is amazing, but because it allows arbitrary JavaScript execution, it’s a massive security risk if you want to allow untrusted users to write content. RDX takes a different approach: it uses the same familiar JSX-style syntax (<Notice...
Farhan Syahleft a comment
Hi Product Hunt! 👋 We love Markdown, and we love components. But as soon as we tried to build platforms where users (not just developers) write content, MDX became a security liability. We built RDX to solve the 'Security vs. Flexibility' trade-off. By treating documents as strictly typed data rather than executable code, we’ve made it possible to have your cake (rich UI components) and eat it...
RDXReactive Document eXpressions: Components as Data, not Code.