EX:OH Feature
We've all seen it happen. You hand over a carefully designed website, and a few weeks later your customer uploads a portrait photo of their new team member into a wide banner. The face gets cropped off at the eyebrows, the text no longer fits next to it, and the support ticket lands in your inbox on a Friday afternoon.
Most of the time nobody did anything wrong. The CMS simply let them change things the design was never built to handle.
EX:OH CMS has been built so your customers can change their content freely, while the layout stays the way your designers intended it.
Every page in EX:OH is made up of sections that come from the theme: a hero, a feature block with an image and a button, a pricing table, a block of text, and so on.
Each section has its own set of fields. Your customer edits the text inline on the page, and changes settings like the image placement or which elements to show through the dialog of that section. They can add and arrange sections in the visual editor, while the markup and styling underneath stay with the theme.
That means a heading always looks like a heading, a button always looks like a button, and nobody needs to know about padding or font sizes to put a new page together.
Themes also decide which page types exist, which of them can sit at the top of a site and which can be nested underneath. When your customer creates a new page, they pick from that list, so the page starts out with the structure the theme expects.
Back to that team photo. When a theme places an image, it can tell the CMS what size and shape the design needs. EX:OH then creates a version of the image to match, so the page loads quickly and the image fits its spot.
To make sure the crop doesn't cut off anyone's head, your customer can open the image in the media library and set its focal point: the part of the image that matters most. Whenever the image is cropped to fit a design, EX:OH keeps that point in view.
Nothing your customer changes goes live straight away. Edits are saved to a draft, which they can preview before publishing, and earlier versions of each page are kept in its version history. Publications can carry a note in the logbook of the page, so when something does go wrong you can see what changed and why.
If you need to dig deeper, the Content Explorer lets you inspect the live copy, the draft and older versions of a page without opening the editor. For larger changes across many pages, Content Tasks let you review each change before it is made.
Sooner or later a customer asks for something their theme doesn't have yet. Copying the whole theme for that one customer means you now have two themes to maintain.
For this we added Component Packs. This new capability introduced in 2026.7 allows theme creators to extend existing themes without having to duplicate all core functionality.
A platform administrator attaches a pack to a theme, and it can add or replace parts of that theme, such as page settings and editor behaviour. The base theme keeps its own release cycle, and the customer gets the extras they asked for.
Your customers get the freedom to keep their website up to date, and you spend fewer Friday afternoons fixing layouts.