For years, building a professional website followed a familiar path: install WordPress, choose a theme, open a visual builder, import a layout and customise it until the site matched the brief.
That workflow was a major leap forward. Divi helped turn web design from a code-only discipline into a visual process, while layout libraries such as Divi Den removed the intimidating blank page. A designer could start with a polished structure and focus on the brand, content and customer journey.
Now there is another way to work.
Instead of assembling every page inside a visual builder, it is possible to describe a business, its audience and the result the website must achieve, then collaborate with an AI coding agent to create and refine a purpose-built site.
We recently tested that workflow on a real project. Using Codex, we built the Tint & Seal window-film website for a local service business in George and the Garden Route. The experience did not make WordPress or Divi irrelevant. It showed us that AI has created a second, genuinely useful path from idea to live website.
Here is how the two approaches compare.
The WordPress and Divi way: build visually from proven parts
A typical WordPress and Divi project begins with a hosting account, a WordPress installation and a collection of design tools. The builder provides the visual system. A layout pack or section library provides the starting structure.
The workflow often looks like this:
- Install and configure WordPress.
- Install Divi and any required plugins.
- Choose or import layouts for the main pages.
- Replace demo content, images, colours and fonts.
- Adjust modules and responsive settings.
- Add forms, SEO, caching, security and other functionality.
- Test, optimise and launch.
This approach remains powerful because so much is already solved. Headers, hero sections, service grids, testimonials, calls to action and blog templates can be selected rather than invented from scratch. Divi also gives non-developers a visual interface for making future changes.
Its biggest advantage is not simply “no code.” It is the mature ecosystem around the site: a familiar content management system, reusable layouts, plugins, user roles, documentation and a large community.
The trade-off is that each convenience adds a layer. Themes, plugins, settings and overrides must work together. A small business site can gradually become more complicated than its actual goals require.
The AI-assisted way: start with the outcome, then create the system
The Tint & Seal project began from a different place. We did not start by browsing page templates. We started with the business problem.
Potential customers usually arrive with one of three concerns: a room is too hot, glare makes a screen difficult to use or clear glass does not provide enough privacy. The website therefore needed to explain the available window-film options, set realistic expectations and make it easy to request an assessment.
Working with Codex, we could describe those goals in plain language, review the implementation and refine the site through a series of focused instructions. The design and code evolved together around the customer journey.
The finished website includes:
- Clear paths for heat control, glare reduction, privacy, UV protection, frosted film and safety film.
- Residential and commercial use cases.
- A simple three-step explanation of the service.
- Local relevance for George, Wilderness, Groot Brakrivier, Hartenbos, Mossel Bay and surrounding areas.
- Practical answers about reflective privacy film, double glazing, fading, warranties and installation.
- A lead form that prepares an enquiry for WhatsApp instead of storing the visitor’s information on the website.
That last detail is a good example of the difference. In WordPress, we might have evaluated form plugins, configured fields, styled the form and decided how submissions should be stored or delivered. In the AI-assisted build, the interaction could be created specifically for the required workflow: collect the useful details, prepare the message and let the visitor choose whether to send it.
WordPress and Divi vs AI-assisted code
| Part of the project | WordPress + Divi | AI-assisted coded site |
|---|---|---|
| Starting point | Theme, layout pack or premade sections | Business brief, content goals and technical requirements |
| Main interface | Visual builder and WordPress dashboard | Conversation, code changes and live previews |
| Design process | Select, combine and customise modules | Describe, generate, review and refine a custom interface |
| Functionality | Usually added with plugins or integrations | Can be implemented for the exact use case |
| Content management | Strong built-in editing and publishing experience | Depends on the system created for the project |
| Maintenance | WordPress, theme and plugin updates | Code, dependencies, hosting and deployment workflow |
| Reuse | Fast through layouts, global styles and saved modules | Fast through components, patterns and reusable code |
| Best fit | Content-rich sites, teams that edit visually and established WordPress workflows | Focused sites, custom interactions and owners comfortable working with an AI coding workflow |
The important comparison is not “manual versus automatic.” Neither method removes the need for decisions. The difference is where those decisions are made.
With Divi, the designer works within a visual system and chooses from proven building blocks. With AI-assisted development, the designer or owner directs the intent while the agent helps translate that intent into code.
What became faster with AI
1. Moving from an idea to a working version
A natural-language brief can become a functional first version quickly. That makes it easier to react to something real instead of debating an abstract wireframe for too long.
2. Making changes across the whole site
A request such as “make the calls to action more consistent” can be handled at the component or code level. When the underlying system is well structured, one change can improve every relevant section.
3. Building small, specific interactions
The Tint & Seal enquiry flow did not need a large form-management system. It needed a short, transparent path from customer details to a prepared WhatsApp message. A focused implementation kept the feature aligned with the business process.
4. Keeping strategy, copy and implementation close together
In a traditional project, the brief, copy document, visual design and development can become separate hand-offs. An AI-assisted workflow can shorten the distance between them. A change to the offer can immediately inform the heading, section order and interface.
What did not disappear
AI can produce code, but it does not eliminate responsibility. Someone still has to decide what the website should say, which claims are supportable, what information a customer needs and what action matters most.
The Tint & Seal website works because it is organised around real customer questions. It explains, for example, that reflective privacy performs differently at night and that film selection depends on the glass and the desired result. Those are business and communication decisions, not decorative details.
The same is true of quality assurance. Responsive behaviour, accessibility, page speed, forms, analytics, SEO, legal pages and browser testing still need attention. AI can help with the work, but “AI generated” is not the same as “ready to publish.”
Where WordPress and Divi still have the advantage
For many projects, WordPress and Divi remain the more practical choice.
If a client wants to publish articles every week, manage a large content archive, give several people editing access or make visual changes without touching a code workflow, WordPress offers those capabilities out of the box.
Divi is also valuable when speed comes from selection. A strong layout library lets a designer compare polished options, combine sections and create a distinctive site without designing every pattern from zero. That is especially useful for agencies producing multiple client sites on a proven platform.
There is also a simple maintenance question: who will own the site after launch? A familiar WordPress dashboard may be a better handover experience for one client. Another owner may prefer asking an AI agent to update the code and deploy a reviewed change. The right answer depends on the people, not only the technology.
AI does not replace templates—it changes their role
Templates solved the blank-page problem for visual website builders. They encoded good design decisions into reusable sections and pages.
AI can use the same kind of design thinking at a different level. A layout may become inspiration, a design-system reference or a specification rather than the final structure imported into a page builder. The most valuable template work—hierarchy, spacing, responsive composition and conversion patterns—still matters.
This suggests a more interesting future than “AI versus WordPress.” Designers can use AI to explore ideas, develop content, create custom functionality or speed up repetitive work while still building and managing the final site with Divi. They can also use established layout principles to guide a custom-coded AI build.
The workflows can compete, but they can also complement each other.
So which way should you build your next website?
Choose WordPress and Divi when you value a mature CMS, visual editing, a large plugin ecosystem and a straightforward handover to people who already know WordPress.
Consider an AI-assisted coded site when the project is focused, the required interactions are specific and you want the implementation to follow the brief without carrying unnecessary theme or plugin layers.
Whichever route you choose, the fundamentals have not changed. A good website still needs a clear audience, a useful offer, trustworthy content, intuitive navigation and a strong next step.
The most important lesson from building Tint & Seal was not that AI makes websites by itself. It was that AI can turn website creation into a faster, more direct collaboration between business intent and implementation.
WordPress and Divi made website building visual. AI is now making custom development conversational. For website creators, that does not close one era. It opens another toolset.
