INTELLIGENT DESIGN WITH A HUMAN TOUCH

An assistant that has read your site and can change it by opening pull requests against your site's own repository, reviewed like any other change.

• It can handle the repetitive work. Updating specifications, changing delivery information, replacing documents, fixing outdated copy, or publishing new content, without anyone having to work through the CMS by hand.
• Give it a plain instruction and it works through the tools and systems connected to your site to make the change, opening the result as a pull request through CI rather than editing anything directly. For sensitive or uncertain changes, it can stop and ask before it goes further.
• Every change is a commit with a history, not an edit nobody can trace afterwards. That is what keeps the site accurate as more people touch it, and it is the reason this layer exists at all: software is heading toward being operated by agents talking to it directly, not only by people clicking through admin panels.

A visual surface for arranging a page, where what you are editing is the page as it will publish.

• Move sections, swap an image, rewrite a heading, and see the result in place rather than in an approximation of it.
• Page builders hand you unlimited freedom, and that is the reason so many sites drift out of shape within a year of launch. Canvas offers the blocks your site was actually designed with, so a page you put together in a hurry still looks like it belongs.
• Nothing you do in Canvas can break the layout on a phone. That is a property of the blocks, not a thing you have to remember.

Your content as structure rather than a pile of pages that happen to mention the same product.

• A product is a product, with its own fields for specification, documents, images and the range it sits in. Write it once and every place it appears follows.
• Draft, schedule, publish, and roll back to an earlier version when someone publishes the wrong price on a Friday.
• Because it is structured, it can be filtered, searched and indexed properly. That is the difference between a catalogue and a list of PDFs.
• The moment your site pairs with the dashboard, whatever is already committed and live is seeded straight into the editor, so it opens with your actual content on day one rather than a blank page.

Image and file handling that stops being a manual chore.

• Upload once and the format, size and compression are handled for you, so the site stays fast without anyone remembering to run it through a tool first.
• Alt text is generated alongside the image, not left for whoever happens to remember accessibility exists.
• Every asset lives beside the content that uses it, in the same structured place, rather than in a folder nobody can find later.

Plain answers on one screen, instead of a dashboard nobody opens twice.

• Which pages bring you enquiries, and which ones only bring you traffic. Those are rarely the same pages.
• Where people stop reading, so you know which paragraph is doing the damage.
• What visitors searched your own site for and did not find. This is usually the most useful list you will read all month, because it is your customers telling you what is missing.
• What visitors think of a page while they are still on it, through feedback attached to that page rather than a survey that arrives a week later.

A way to show work before it is public, without publishing it to the world first.

• Set an access code on a site or a page, and only the people you give it to can see it. Useful for a sign off, or a launch that is not ready for Google yet.
• An alert lands when someone actually opens it, so you know a preview has been seen rather than wondering.
• Turn it off the moment the site is meant to be public, and it behaves exactly like any other page from then on.