PRACTICAL AI / WEBSITE DEVELOPMENT

Build the page quickly.Make the next edit easy.

The first version is rarely the expensive part. The cost arrives when a small change disturbs a working page. Use AI to build reusable controls, then assemble pages people can maintain.

01 / THE MAINTENANCE DECISION

Optimise for the tenth edit

Ask who will change the page next month. Their answer should shape the architecture before the first page is generated.

THE DECISION IN PRACTICE

Why KJM moved from complete HTML pages to controls

Complete HTML pages let us build fast. The weakness showed up in maintenance.

What worked

AI produced layout, wording, styling and interaction in one pass. Ideal for proving a concept.

What became expensive

Every change meant returning to a large block of code. Regeneration sometimes broke something that already worked.

What we changed

AI now builds reusable web controls based on the designs of the original HTML page it created, then creates page templates that use them. Text, cards and links stay in editable fields. Shared behaviour stays in the component library.

The test of success: fully automated content creation with the next content change happening without asking AI to rebuild the page.

WHEN TO BREAK THE RULE

A prototype is allowed to be disposable

A single HTML page is still a good way to test an idea. Before it becomes a permanent feature, decide what an editor needs to own and what should be shared. Not every one-off visual needs a new control.

02 / KNOW THE BOUNDARY

Give the website nothing worth stealing

A public website can hold sensitive data securely, but only with specialist security expertise behind it. Most organisations don't have that, and AI doesn't replace it. So keep the site's job small: present information and pass enquiries on. Customer and staff records stay in your internal systems, protected by identity controls you already pay for and that Microsoft or Google maintain at a scale few organisations could match. The site still needs protecting, but a breach there should not expose your business.

Public

Public content and presentation

Built and tested with public content only.

Service pages, card layouts and navigation can be built and tested with public content. Keep the platform, plugins and deployment process maintained, whoever wrote the code.

Low value to an attacker.

In transit

Enquiries passing through

The site collects details. It shouldn't keep them.

When someone fills in a contact form or chats with an AI assistant, their details should go straight to your internal systems. Many tools quietly keep a copy along the way, in form plugins, email notifications or activity logs. Check each one and switch off or clear anything you don't need.

No customer details left on the site.

Internal

Records kept behind the login

Sensitive information never sits on the website.

Customer history, staff details and anything that changes important records stay in your internal systems. Only authorised people who sign in with their work account can reach them. Don't let the website hold passwords or open direct links into those systems, even to make a demo easier.

A breach of the site stops at the site.

DESIGN FOR FAILURE

Reduce the consequence of compromise

Keeping records off the public site limits what an attacker can take. It does not make a compromised site harmless: content can be altered, submissions captured or visitors redirected. Protect and monitor the site anyway.

03 / DECIDE WHAT CAN CHANGE

Separate the words from the workings

Every reusable control on your site needs a clear split. Editors change the words, images and links. The control handles layout, spacing and how it looks on a phone. Left to itself, AI will add a setting for everything, and you end up with something harder to use than the page it replaced. Only add a setting when someone will actually need to change it.

READY-MADE PROMPT

Let the master prompt build it this way

Our master prompts are available for you to test and use freely, click the button below and select the task. Submit a comment for requests, suggestions and feedback. 

Platform check

What can your website platform do?

Search for the platform your site runs on. If it uses a page builder or theme, pick that too. You will get a plain-English view of how far this guide's approach can go on your setup.

    Platforms change their features and plans often. Treat this as a starting point and confirm with your provider before committing. Not listed? Choose "Other or not sure".

    04 / CONTROL THE CHANGE

    Keep changes controlled and reversible

    "Make it better" gives AI permission to redesign everything. A good request names the problem, says what must stay the same and explains how you'll know it's fixed. Keep each round of changes manageable. The more you change at once, the harder it is to see what the AI touched and why.

    Make versioning automatic

    Put the standing rules below in your AI tool's instructions, or at the top of your master prompt. Every change then produces a new numbered version, complete with all files, and the previous one is kept.

    Store them yourself. AI can number versions but can't be trusted to keep them. Save each accepted version somewhere you control.

    Describe the change precisely

    Say what should change, what must stay the same and how you'll know it's right. Tell the AI to reuse what already exists, such as shared lists, settings and controls, instead of building a second copy. Duplicates pass testing and only show up later, when you update the original and the copy doesn't follow.

    Then think ahead: what might need to vary in future, such as themes, brands, languages or regions? Tell the AI now so it's built as a setting from the start. Adding flexibility later means reworking everything that was written for a single case.

    Read the change log

    Every response lists what changed, what was tested and what couldn't be checked. Challenge anything you didn't ask for.

    Watch for warning signs. Files you didn't mention, or a long list of changes for a small request.

    Make AI remove unused code

    AI tends to leave old code behind when a change replaces it. Left in place, it adds clutter, confuses later changes and can still cause faults. Ask the AI to remove anything the change has made redundant, but only after it has checked everything that might depend on it. Your previous version stays untouched, so you can restore anything removed by mistake.

    WHEN FIXES STOP WORKING

    Ask for a fresh design, not another fix

    AI prefers to add to existing code, so a badly designed part gets patched again and again. When the same issues keep returning, stop asking for fixes and ask for a design review instead.

    Step 1: ask for the review.

    "The issues below keep repeating. Look at the affected code from first principles and tell me how you would design it differently if starting from scratch. Cover only the part that's causing the problem, not the whole project. Explain what's wrong with the current design, what you'd change and what it would affect. Check the architecture reference first. Don't write any code yet.

    The problem: [describe it here]"

    Step 2: approve the design, then build.

    "Go ahead with that design. Replace the old version of this part completely instead of running both. Deliver it as the next version number, and keep the previous version available."

    05 / ACCEPT THE RESULT

    Test it yourself before you accept it

    Have the AI validate every change before it hands it over. It catches many faults, but not all of them. It can't see your screen the way you do, and it can build something that works but doesn't suit your site or your audience. Nothing should reach your users until you've approved it.

    Make AI validate first

    Ask it to test every change before delivering it. That means very long and very short text, empty optional fields, two copies on one page and anything the change could have affected. It should report what it checked and what it couldn't.

    Check how it looks

    Visual faults are where AI is weakest. Look for spacing, alignment, colours, text that wraps badly and anything that looks slightly off. 

    Question the design itself

    A control can pass every test and still be wrong. It might be too complicated, inconsistent with the rest of your site, or built for a case you don't have. Challenge whether it's what you'd have asked for.

    Test on a staging site first

    Never try a change on your live site. Use a test or staging copy, so mistakes never reach your users. If your platform doesn't offer one, use a private, unpublished page.

    Then check it live: Once released, look at the published page on a phone and a laptop, follow every link and try it with only a keyboard. Caching, missing components and security settings can cause different behaviour there.