Every CMS asks the same first question: "Pick a template."
You scroll through hundreds of thumbnails, choose the one closest to what you had in mind, and spend the next three weeks bending it into shape. The hero is the wrong height. The footer has a section you don't need. The About layout assumes a team of twelve, and you're three people.
That question made sense when the alternative was hiring a designer and a developer. It makes less sense now.
Why templates existed
Building a design from scratch was expensive. A template was a shortcut: someone else had already done the design and the code, you paid a small fee, and you got most of a website on day one.
The rest was the price of the shortcut:
- Your site looks like thousands of others, because it runs the same theme. Visitors have seen it before, even if they can't say where.
- Spacing, fonts, section order and mobile menu behavior were decided for a generic customer who isn't you.
- Themes ship with options, scripts and styles you will never use, and your site loads all of them anyway.
- Every change fights the template's structure, and a theme update can break what you customized.
We watched customers go through this for years. The template was rarely what they wanted. It was what they could afford.
Design stopped being the expensive part
Today you can describe what you want to an AI and get a working design back in minutes, with your colors, your tone, your sections and your layout. It comes as real HTML and CSS, not a mockup.
That moved the bottleneck. Producing the design used to be the hard part. Now the hard part is getting it into your CMS, and that is where a template-based system gets in the way, because it wants your design to fit its structure.
So the question flips. Instead of asking which template is closest to your idea, you decide what you want your site to look like and let the system adapt.
From idea to live page with Neleto and MCP
Neleto has a built-in MCP server. It is part of the core, not a plugin. An AI assistant like Claude can work directly in your CMS: create pages, set up layouts, write content, upload images. It follows the same permissions a human editor has.
The workflow looks like this:
- Describe the design. For example: "A calm, editorial look for a family-run bakery. Warm off-white background, one strong orange accent, large photos, short sections."
- The AI builds the layout and components in your own HTML and CSS.
- Through MCP, the assistant creates the layouts, pages and content in your CMS. You don't copy and paste, upload zip files or run a theme installer.
- You refine in conversation: "Make the hero shorter. Add an opening-hours block above the footer." The change lands in the same place.
Your editors still get a clean admin interface for everyday content. The design underneath is yours, not a stock theme with your logo on it.
"But I don't know how to design"
You don't have to. You know what you want, even if you describe it as "friendly" or "not too corporate". AI is good at turning a description like that into a layout. If you have a logo, a brand color or a site you admire, hand those over as a starting point.
If you do have a designer, the same path works. Bring a Figma file or finished HTML and let the assistant implement it. See how we turn existing HTML into a Neleto site.
Won't every site turn into a mess?
It's a fair worry. Three things keep it in check.
Layouts and components are reusable. Once the header, footer and content blocks exist, new pages are assembled from them. Templates gave you that discipline too, but now the system is yours.
You give the AI your brand colors, fonts and spacing once, and it applies them across every page.
And nothing goes live until you're happy. If the first draft isn't right, ask for changes.
Starting point, not villain
If a ready-made design is exactly what you want, use it. But it shouldn't be the only route to a good-looking website, and it shouldn't be the first thing a CMS asks you.
Start with your idea. The design follows, and the CMS keeps up.
Try it yourself: Start free on Neleto, connect Claude, and describe the website you'd build if templates didn't exist.
Top comments (0)