The CMS

The problem it solves

Every site I handed over became a small debt: a WordPress to keep updated, plugins arguing with each other, a contact form that quietly stops working in September, and the client writing to me because the site is mine.

The uncomfortable truth is that ninety per cent of the sites I build don't need a database running on every visit. They need pages that load instantly, that somebody can edit without calling me, and that don't fall apart on their own in the meantime.

That's where this came from: you write it in a visual editor, it comes out as static HTML. The panel is for me and for whoever wants to manage their own content; the visitor gets files that are already finished.

What runs on it

This isn't a prototype full of placeholder content. These are real clients, who pay, using them every day:

• Amministratore Pro, a property management firm: site, guided quote request and a registration form that generates the PDF
• Claudia Magni Wedding Planner, Italian and English, with real wedding pages and call booking
• Sardelli Iliano, electromechanics: service catalogue and repair requests
• Magnacarta Eventi, wedding stationery
• alessandrotofani.it, mine, case studies included

And this one you're reading. rodion.it is built with Rodion too: if the editor couldn't take daily use, I'd be the first to notice.

For the people who appreciate details

Pages are rendered with the same React code as the preview, then frozen into HTML. The parts that need to stay alive (forms, accordions, bookings, scroll-linked effects) come back with plain JavaScript, no framework on board.

Images go out in four widths plus the modern format, with dimensions declared so the page doesn't jump while it loads. Scripts are bundled into separate cacheable files. The result is a site with no database to attack, no security updates to chase, and one that keeps working even when the panel is switched off.