Fixed: your website renders the way you wrote it

CallPages websites render authored content the way it was written again: images written into a page appear as images, and the top navigation shows your sections in one styled row instead of an endless link list. A regression in the site renderer had dropped those rules; they are restored and now pinned by tests.

Owners reported their websites had collapsed into long lists of blue links — every product photo gone. The pages’ data was never touched; the renderer had lost two rules in a wholesale code merge: the rule that turns image markup into images, and the rule that caps and styles the top navigation. Because the data was intact, the fix is a restoration, not a rebuild — and the guard against it happening again matters as much as the fix.

What visitors were seeing

For several days, tenant websites rendered as if their styling had been peeled off: the words were all there, but images written into pages came out as bare links and the navigation sprawled. Nothing about the owners’ content had changed — every page, product, and photo was intact in the database the whole time. What broke was purely the translation from stored content to the rendered site.

How it happened, plainly

The site renderer is shared code, and a large merge brought in an older copy of it — a copy from before two rendering rules existed. Merges like that fail quietly: the code is valid, the pages load, and only the output is wrong. The two lost rules were the image rule (image markup in authored content becomes an image element) and the navigation rule (sections are capped and laid out in one styled row).

The restoration — and the guard

Both rules are restored, and production websites render as authored again: photos where the owner put them, navigation as one row. The durable part of the fix is procedural: the tenant-website test file exercises exactly these rules, and a red run on it now blocks a merge instead of being waved through. Regressions of this class — valid code, wrong output — are precisely what a rendering test suite exists to catch, and it is wired into the gate now.

Nothing to redo

Because the data never broke, there is nothing for owners to repair: no page to rewrite, no photo to re-upload. If your website looked wrong this week, reload it — it is the site you wrote.

How it works

1. The renderer again converts image markup in your website pages into real images — what you wrote is what visitors see, photos included.
2. The navigation rules are restored too: your sections lay out in a single styled row, capped the way the design intends.
3. The website test suite that covers these rules now blocks merges: a red run on the tenant-website tests stops a release instead of shipping alongside it.

See it live: Mi Junta

Mi Junta — CallPage · Mi Junta — website

A tenant website on production, captured 2026-10-16 after the fix: the banner and the product imagery render as real images again, and the sections sit in one navigation row — the site the owner wrote, not a list of links.

See a CallPages website →