---
title: "Do you need an AI coding course to build your first website?"
url: https://iwantaito.com/blog/do-you-need-an-ai-coding-course-to-build-your-first-site/
summary: "Not to get a first site live. Describing it to Claude and learning to check the result gets you further. A course pays off once you want to change the code yourself."
published: 2026-10-20
updated: 2026-10-20
author: "Jack Stovell"
publisher: "Adapt Progress Evolve Limited"
language: en-GB
---

# Do you need an AI coding course to build your first website?

Not to get a first site live. Describing it to Claude and learning to check the result gets you further. A course pays off once you want to change the code yourself.

Short answer: before you look at any courses, decide what you want to end up with. If it is a page you can send someone a link to, you can start today with a Claude chat. If it is understanding code well enough to write it yourself, a course earns its place, usually a bit later.

Search for an AI coding course and the results answer several different questions at once: videos on how AI works, courses for teachers, classes for children, long lists of platform courses and forum threads. They help someone, but rarely the person who just wants a website by the weekend.

## Three different things people mean by 'AI coding course'

"Learn AI", "learn to code" and "build something with AI" sound like one goal. They are three.

Learning AI means understanding how these systems work: models, training, and what they can and can't do. It's interesting, and you can finish all of it without having a website.

Learning to code means writing and changing the instructions a computer follows, yourself, line by line. It's a real skill and it takes real time.

Building something with AI means you describe what you want in plain English, Claude writes the files, and you check them and put them live. You end up with something to show people, and you didn't need the first two to get there.

Most people who type that search want the third. They just haven't separated it out yet.

## If you want to put something live: what you actually need to learn

Three things, and none of them is programming.

1. Describing what you want clearly. That is a writing skill: who it's for, what goes on it, what it should feel like and what to leave out.
2. Reading what comes back well enough to spot when something is off.
3. Getting it from a chat onto the internet. On the build pages here the main path has no terminal. The developer steps sit in a collapsed "For developers" section you can ignore.

To see the describing part, the [website build](/asks/build-me-a-website/) shows the plain-English prompts and Claude's unedited replies for a three-page site. The walking group and the walks in it are made up, and the page says so. Every build page uses made-up people and businesses.

## The skills you pick up by building, and where to see them

You skip the course and still learn things, because you need them.

**Reading files.** In the website run Claude saved four files: index.html, walks.html, about.html and style.css. Look at those a few times and you soon know that index.html is the home page and the .css file holds the look. When we later asked for a new walk, Claude listed the two files it had changed, which tells you exactly which ones to upload again.

**Checking on a phone.** A page that looks fine on a laptop can be awkward on a small screen. On the [CV website](/asks/build-me-a-cv-website/) the small capital labels were still 12.8px after Claude's own check. That is easy to read on a laptop and small on a phone. Opening your page on your own phone catches that kind of thing in seconds.

**Asking it to check its own work.** The first version of the [game](/asks/make-me-a-game/) had five failures, including not pausing when the phone was turned sideways. Claude found them itself when asked to check, and fixed them. On the [landing page](/asks/build-me-a-landing-page/), Claude only spotted that its form's messages never showed because a prompt asked it to try to break the form. Knowing to ask for that check is a skill no theory course will teach you.

**Publishing.** Getting files from your computer to a real web address sounds daunting. Mostly it comes down to uploading files and following the screens. Each build page ends with the steps and lists what Claude got wrong about them.

## When a course is worth it

A simple test: do you want to change the code by hand, or do you just want the result?

If you're happy to describe a change and let Claude make it, a course isn't what stands between you and a live page. If you keep wanting to tweak things yourself, want to know why something works, or want to work with code as part of a job, paying for structure starts to make sense.

Another sign: you've built a couple of things, you keep hitting the same wall, and you can tell the wall is a gap in understanding rather than a vague prompt. That's a good moment for a course. Before it, you're mostly paying to be told things you'd learn faster by doing.

A course is a fine purchase. It's just a poor first purchase if the goal is a live page.

## How to choose a course without a ranking list

We don't rank or name courses here. Prices, lengths and contents change, and we haven't taken them. What we can give you is how to look:

- Read the course's own page, not someone's summary of it.
- Check that it matches your goal. A course on how AI works won't teach you to publish anything.
- See whether you make something real during it, or mostly watch.
- Look at who it's really for. "Beginner" means very different things on different pages, and some of the top search results are aimed at teachers or children.
- Be wary of big promises about speed or jobs.

## A sensible first week if you build first

1. Decide what you want to end up with: one page with one purpose. A landing page for a class, a CV or a simple game.
2. Follow the [start page](/start/) to get set up rather than making up your own route.
3. Describe the thing in plain English, and ask Claude to tell you its plan before it makes anything.
4. Open what comes back on your laptop, then on your phone.
5. Ask Claude to check its own work, then fix what's wrong one thing at a time.

By the end of the week you'll have something to look at and probably a list of questions. Those questions are your syllabus, and they'll tell you whether a course should be your next step.

## What to do when you get stuck

You will get stuck, and that's fine. Tell Claude exactly what you see, in your own words. "The button is there but nothing happens" is a perfectly good bug report. Paste in any error message exactly as it appears. Change one thing, check it, then move on to the next.

If what worries you is what AI can and can't do for you at all, [can I use AI to build a website](/blog/can-i-use-ai-to-build-a-website/) covers that side. This post is only about how you learn.

## Sources

- [iwantaito: I want AI to build me a website (recorded run)](https://iwantaito.com/asks/build-me-a-website/)
- [iwantaito: I want AI to build me a CV or portfolio website (recorded run)](https://iwantaito.com/asks/build-me-a-cv-website/)
- [iwantaito: I want AI to make me a game (recorded run)](https://iwantaito.com/asks/make-me-a-game/)
- [iwantaito: I want AI to build me a landing page (recorded run)](https://iwantaito.com/asks/build-me-a-landing-page/)

## Questions people ask

### Do I need to learn to code before using AI to build a website?

No. You need to describe what you want clearly, check what comes back on a laptop and a phone, and follow the steps to put it live. Coding can come later if you want to change things by hand.

### What is the difference between learning AI and learning to code?

Learning AI means understanding how these systems work. Learning to code means writing and changing the instructions a computer follows yourself. You don't need either to get a first site live with Claude.

### How can I learn coding as a beginner?

Build something small and look at the files you get back. You learn which file does what, how to check a page and how to publish it because you need to. If you later want to write the code yourself, structured teaching helps then.

### When should a beginner pay for a course instead of just building?

When you want to understand or change the code yourself, or when you keep hitting the same wall and can tell it comes from not understanding something rather than from a vague prompt. Until then, building is usually quicker.

### What should I check before paying for an AI coding course?

Read the course's own page. Check that it matches your goal, that you make something real during it, and who it is really for, because 'beginner' means different things on different pages. Be wary of big promises about speed or jobs.
