Core system
Client-editable content
You change the words and images. You cannot break the design.
What it is
A content layer scoped to exactly what should be editable — copy, images, video, SEO fields — while the layout stays locked. It is the difference between a site your marketing team runs and a site they have to email us about.
How we build it
What makes ours work
We scope what is editable before building the editor
The first decision is not which CMS to use — it is which parts of the site should change without a developer, and which should not. Copy, images, video, campaign banners and SEO fields: editable. Layout, spacing, typography and structure: locked. That boundary is agreed page by page, then the editor is generated to mirror it, section by section, so your team edits the site they recognise rather than an abstract tree of fields.
Constraints do the work that training usually fails to do
CMS disasters are usually permission disasters — someone could break the layout, so eventually someone did. Our fields carry constraints instead of warnings: images crop to the slot they fill, headings have length limits that protect the design, and every field has “reset to original” so an experiment is never fatal. The iCAUR marketing team edits every word and image on a launch-grade automotive site, and cannot break it, because breaking it was never made possible.
Publishing is instant and the site stays fast
An editable site must not become a slow site. Our content builds render pages once, serve them from cache at the edge, and refresh exactly the pages an edit touched — so a saved change is live in seconds while visitors keep getting cached-speed responses. On iCAUR, edits go live in about four milliseconds of server work per page view, which is to say: the CMS costs the visitor nothing.
Proof
Where we've built this
Every build below contains this system. Open any one and click through it — the fastest way to judge whether we can do what you need.
Questions
Asked about content studio (cms)
The questions that come up when we scope this system. Anything else, ask us directly.
Is this WordPress?
No — it is a content layer we build into the site itself, scoped to your pages and fields. WordPress is a fine tool we still work with when it fits, but for launch-grade custom sites a purpose-built studio avoids the plugin sprawl, update treadmill and security surface, and it gives your team an editor that exactly matches the site instead of a generic admin. The right call depends on the project; we will tell you honestly which fits.
Can we add new pages ourselves?
Where new pages follow a pattern, yes — that is a template we hand you. On iCAUR, the client creates a complete new vehicle page by typing a name and address: the page is generated from the existing model template, appears in the navigation and sitemap automatically, and every section is then editable. Genuinely new page designs remain design work, which is the point of the boundary.
Can you migrate content from our current CMS?
Yes. We extract the content that matters — pages, copy, images, SEO titles and descriptions — clean it up, and load it into the new structure so launch day does not start from blank fields. Preserving your existing SEO metadata during migration is part of this, and where URLs change we map redirects so accumulated search equity is not thrown away.
Do we need training to use it?
A short handover session, usually under an hour, is enough — because the editor mirrors the site page by page, your team already knows where everything is. The constraints mean there is no list of things to be careful about, and “reset to original” means mistakes are reversible. The real measure: client teams make their first unassisted edit the same day.
Need this in your project?
Tell us what you are building and we will show you the closest thing we have already made — then quote the real version.
Tell us what you need built
We'll put together a free working prototype of your project so you can click through it before paying anything.