So, my manager has decided to explore Paligo's Nexus tool. And as bad as their UI and workflow are for normal publication flows, this thing has managed to accomplish something I would have thought impossible: it's somehow worse.
The first problem is their theme tool. It's supposed to be a VS Code plugin that claims "For an edit loop without uploading, the Paligo Theme Studio extension for VS Code renders a theme folder against a real publication as you save." Except that description bears almost no resemblance to what it actually does.
Paligo hands you a folder full of Twig, CSS, and JS, then tells you it’s a “theme” as if you’re building a normal front-end app. In reality, you’re packaging a server-rendered publication template, uploading it to their platform, and then waiting for their backend to reassemble the whole docs site with your design bolted on. It’s not “live preview” in any meaningful sense. It's a long, fragile chain of packaging, uploading, and rendering. That's not a theme. It’s a hostage note to a render pipeline.
And the “customization” isn't a theme layer either. It's a late-stage JS patch job: the page is rendered by the platform, then the client-side script injects the branded content, images, and structure at runtime. The “customized” experience is not actually the template: it's an assembly that occurs in the browser after the fact. What's really happening is that they're shoveling brand assets, nav chrome, and layout bits in via JavaScript when a page loads. Their marketing text is an overly elegant way to describe a system that is, under the hood, rendering a shell and then layering the “real” design on top with script, like too much makeup trying to cover the ugly underneath.
Each render takes over three minutes (yes, I timed it) so if you want to tweak an element and see what changed, that's a three-minute wait... each time. Color not quite right? Three minutes before you can see if your change worked. Font size a little too small? Three minutes before it renders with new headings. Logo cropped funny? Three minutes before you can see if your edit fixed it. Every time, the platform has to repackage the bundle, upload it, validate it, and re-render the publication on the server before you can even see whether a change did anything useful. That is not “live editing.” My smallish sample taking three minutes is a reminder that what's really happening with every edit is a server-side deployment with a side of disappointment.