You know the feeling. You’re building an admin panel, and the client wants a visual editor. You glance at TinyMCE, Quill, ProseMirror… all the same promise: drag-and-drop, real-time editing, no HTML. Then you spend two weeks wrestling with CSS bleeding, plugin hell, and a bundle size that makes your CI pipeline cry.
I’ve been there. Every developer I know has been there. The page builder industry has sold us a lie: that we need to recreate the browser’s rendering engine in JavaScript. And they’re doing it badly.
The dirty secret of the page builder industry is that they’re all trying to rebuild the browser’s rendering engine in JavaScript. And they’re doing it badly.
So what if you just… let the browser do its job?
That’s exactly what Neiki Page Editor does. It’s a simple web component that loads real HTML and CSS into an isolated <iframe>. You edit visually, save the result back through your own handlers. No CSS specificity wars. No bloated dependencies. Just the browser’s native rendering engine, sandboxed and reliable.
I saw a demo where a developer dumped a 300-line CSS file into this editor and it rendered pixel-perfect. No bleed, no override. Just the browser being the browser. That’s the kind of moment that makes you rethink everything you thought you knew about rich text editors.
The most robust architecture is the one that admits its own limits.
This isn’t just a clever hack — it’s a fundamental shift in how we think about embeddable editing. Most WYSIWYG editors are heavy page builders trying to emulate the browser’s CSS cascade. They fail because they reinvent the wheel, badly. By surrendering control back to the browser via a sandboxed iframe, you get pixel-perfect rendering with zero fighting.
It’s the perfect compromise between a lightweight rich-text editor and a heavy page builder. You get the fidelity of a real web page without the technical debt of a full-scale builder. And it’s embeddable into any CMS or admin panel in minutes.
The best page builder isn’t a page builder at all. It’s a hole in the wall — a window into a real web page.
Next time someone asks you to integrate a visual editor, ask yourself: do you want to fight the browser, or embrace it? The answer is simpler than you think.
FAQ
Q: Doesn't an iframe introduce performance or security issues?
A: Yes, but they're manageable. The iframe is sandboxed so it can't access the parent's DOM. For editing UIs, the performance is negligible because you're only rendering a single page. Plus, you get true CSS isolation without any hacks.
Q: What's the practical implication for my team?
A: You can ship a visual editor in days instead of months. No need to maintain a custom CSS reset or fight with editor plugins. The browser handles all the heavy lifting. Your team focuses on the actual editing logic, not the rendering engine.
Q: Isn't this just reinventing the wheel? Every editor has an iframe option.
A: Most editors use an iframe for content isolation but still try to inject their own CSS and JavaScript to emulate a browser. This editor does the opposite: it loads real HTML and CSS directly into the iframe with zero transformation. It's not a wheel — it's letting the wheel roll on its own.