Generating a page layout is the cheap part. The harder job is checking whether the output will work in the builder where you need to use it.
With YOOtheme Pro, a file can be valid JSON and still give you stacked columns, missing images or buttons that ignore the style you asked for.
YOOforged checks generated layouts for known YOOtheme compatibility problems before you download them. The aim is to save you from finding those problems one by one after import.
Where a valid file goes wrong
YOOtheme Pro imports layouts as JSON files. But valid JSON only tells you the file follows the format’s rules. It doesn’t tell you whether the settings mean anything to YOOtheme.
Take a three-column row. The row can describe the right arrangement while its columns have no width settings. Those columns can then display at full width, turning the row into a stack.
Other mistakes are less obvious. A button’s style can sit on the container instead of the individual button. An image address can be stored in a field the element never reads. You can see the intended setting in the file, yet it has no effect on the page.
Catching these errors means knowing which settings YOOtheme actually uses, where they belong and how they work together. That’s the difficult part of verification.
What YOOforged checks
After generation, YOOforged runs checks on the layout and repairs problems it recognises. These include:
- Rows and columns. It fixes common mismatches between a row’s layout and its columns, and fills in column widths.
- Image fields. It corrects familiar field-name mistakes so image addresses are stored where the element expects them.
- Element settings. It removes unsupported properties from the element types it checks and corrects several known setting mistakes.
These are specific repairs. Correcting an image field, for example, doesn’t prove that the image at that address is still available.
Convert also removes custom CSS and class properties from generated elements. It aims to recreate the page with native YOOtheme elements and settings, so you can keep editing it in the builder.
That matters after the first import. When a client asks for a different button style or another column, you want to make the change through the controls you already use. A layout is more useful when you can maintain it that way.
Some checks are better handled by code
Colour contrast is a useful example. In Style mode, the model proposes design choices, and YOOforged calculates the palette from them. It then checks key text and background combinations.
Code can measure the contrast between those colours. These checks don’t establish contrast for every part of a finished page, especially text over images or colours changed elsewhere on the site.
You still need to open the page
YOOforged’s checks cover known compatibility problems. They don’t render and inspect your page, check whether the copy is true, or prove that every section survived a conversion.
After import, compare the result with your source. Check the text and section order, open the links, replace missing images, and look at the page on desktop and mobile. A screenshot alone can’t supply the destination behind a button, and images bundled in a design export still need to be uploaded to your site.
Why this work matters
AI page building is becoming more common. Bricks 2.4 added AI-assisted page creation and editing, and YOOtheme has announced a first look at its own AI plans. Producing more layouts makes checking their output more important.
For YOOforged, the useful work is in those details: catching a missing width, correcting an image field, removing a setting the element can’t use. Each is a problem you’d otherwise have to track down yourself before getting on with the page.
Convert your HTML to a YOOtheme Pro layout
