Free course · Beginner

Your website online, without friction

Start from scratch. Create a page with AI. Keep its code in GitHub. Publish with Netlify. Connect a domain with Cloudflare.

7 modulesAt your own paceText, exercises and quizzes
Start learning
01

Understand the chain

One tool. One job. You stay in control.

By the end of this module

Trace the route from an idea to a working website.

AI helps you write the code. GitHub keeps the files and their history. Netlify builds and hosts the website. Its URL already lets people visit it. Cloudflare can manage the DNS that connects your domain to that hosting.

We will build a small static website. Static means the pages are prepared before someone visits. Customer accounts, databases, payments and an AI assistant inside the site require additional services and checks.

You can follow this course with a browser and a text editor. The exercise needs no terminal. Prepare an email address, a GitHub account and a Netlify account. Cloudflare and the domain come later.

Your turn

  1. Choose a practice project, such as a page about your work. Write its title, a short introduction and the action you want a visitor to take.
  2. Create your accounts on the official websites. Enable two-factor authentication and keep recovery codes somewhere safe.
  3. Write down each tool’s role. GitHub holds your code. Netlify serves your published site. A registrar registers your domain name.

What free plans allow

You can reach the Netlify URL using free plans. A custom domain usually involves an initial purchase and an annual renewal.

When to pay, and why

Learning this workflow requires no paid subscription. Start by identifying a measurable need.

Watch out for this

A preview URL may be accessible to anyone who knows it. A private repository does not automatically make the website private.

Your exercise

Explain AI → GitHub → Netlify → URL → DNS to someone in one minute.

Check your understanding · Which tool hosts the pages in this course?

Next module
Official sources
02

Build with AI

Ask for something small. Try it yourself.

By the end of this module

Get a simple page you can understand and edit.

Choose ChatGPT, Claude or another coding assistant. Describe the outcome, audience, content and constraints. Start by asking for one index.html file.

AI output can contain mistakes. Open the result, click everything and check the words. A good-looking page may still have broken links or poor keyboard access.

Here, AI helps during creation. Visitors do not call an AI API. You therefore need no API key in the site.

Your turn

  1. Paste the prompt below into your assistant. Replace the items in brackets with your own information.
  2. Ask for the complete file. Save the code as index.html with UTF-8 encoding. Check that its name is not index.html.txt.
  3. Open the file in your browser. Make the window narrow. Use Tab to move between links and Enter to activate them.
  4. Ask for a specific fix when needed, such as “The button overflows at 320 pixels. Fix only this issue and return the full file.”
Create an English website for [activity], aimed at [audience].
One index.html file with embedded CSS and no external dependencies.
Content: [title], [introduction], [call to action].
Support mobile from 320 px, semantic HTML, readable contrast and visible keyboard focus.
Invent no clients, figures or testimonials. No form or advertising tracking.
Explain how to save and open the file, and state its limitations.

What free plans allow

Assistants offer free access with varying usage limits. If you reach a limit, wait for it to reset or reduce your request.

When to pay, and why

An AI subscription becomes useful when limits regularly interrupt your work or you need a specific tool. API billing is separate from ChatGPT billing. Check any credit benefit separately.

Watch out for this

Keep passwords, private keys and confidential data out of prompts. Never publish an API key inside index.html.

Your exercise

Edit a sentence yourself in the file, reload the page and check the change.

Check your understanding · Do you need an API key to publish the page made with AI?

Next module
Official sources
03

Keep your code in GitHub

Every change leaves a trace.

By the end of this module

Create a repository and save your first version.

A repository is your project folder. A commit saves a version with a message. A branch lets you prepare changes alongside the main version.

Start with main and a site containing no sensitive data. Later, you will create a branch and a pull request, which asks for changes to be reviewed and merged.

Your turn

  1. On github.com, choose New repository. Use a simple name such as my-first-site. Choose Private and select Add a README file. Create the repository.
  2. Choose Add file → Upload files and upload index.html at the repository root, next to README.md.
  3. Select Commit changes. Write “Add first page”. Check that index.html appears in the file list.
  4. Open index.html and its editor. Fix one sentence and save a second commit with a clear message. Open the history and find both versions.

What free plans allow

GitHub Free lets you start with public or private repositories. Netlify builds this course’s site, so the exercise needs no GitHub Actions workflow.

When to pay, and why

Consider a paid GitHub plan when you need collaboration, review or administration features beyond your current plan. Check the relevant features and quotas before upgrading.

Watch out for this

A private repository protects access to its code. Check the visibility of the published site separately.

Your exercise

Find your latest commit and read its message. Explain which file changed.

Check your understanding · What is a commit?

Next module
Official sources
04

Publish with Netlify

Your file. A working URL.

By the end of this module

Deploy the repository and open the live site.

Netlify can fetch your GitHub repository and publish changes from the branch you select. This is continuous deployment.

Our HTML file needs no compilation. An Astro project does need a build command and an output folder. Use settings that match your project.

Your turn

  1. In Netlify, create a project, choose Import an existing project and select GitHub. Connect my-first-site. Grant access to the repository you need.
  2. Choose main. For this HTML project, leave Build command empty and enter . as Publish directory if requested. The dot means the repository root.
  3. Deploy the project. Wait for Published or Ready. Open the .netlify.app address shown by Netlify.
  4. Check the words, links and mobile layout. If the website asks for a Netlify login, review its access controls and make it public once its content is ready.

What free plans allow

The Netlify URL lets you start without buying a domain. The free plan has usage limits. Review Usage & billing before sharing widely.

When to pay, and why

Upgrade when measured usage, teamwork or availability needs exceed your plan. A free service may stop serving the site when its limits are reached.

Watch out for this

A 404 often means the wrong publish folder or filename. index.html must sit directly inside the published folder.

Your exercise

Open your Netlify URL in a private window and on your phone.

Check your understanding · Which settings fit the exercise’s HTML file?

Next module
Official sources
05

Update with confidence

Test it. Then publish.

By the end of this module

Check automatic deployment and learn to fix a mistake.

A commit on main triggers a publication when main is the production branch. Use a separate branch to prepare a bigger change.

A pull request connects your branch to main. With Netlify Deploy Previews enabled, it can receive a test URL. Wait for the build to finish before sharing it.

Your turn

  1. On GitHub, open the branch selector and create try-title from main. Edit the title in index.html and commit to that branch.
  2. Open a pull request into main. Review the checks and the Netlify preview link if available. Inspect the page before merging.
  3. Merge the pull request when the page is ready. Check the published commit in Netlify, then reload the live website.
  4. To repair a simple change, edit the incorrect sentence in GitHub and save a corrective commit. Check the next deployment.

What free plans allow

This basic workflow works on free plans within their limits. A preview does not guarantee privacy and may use resources.

When to pay, and why

Pay for more build capacity, team controls or protection when your project needs them.

Watch out for this

If a build fails, read the first useful error in its log. A failed publication generally leaves the last successful publication in place.

Your exercise

Make a small correction and check that the published commit matches it.

Check your understanding · Your new build fails. What should you do first?

Next module
Official sources
06

Connect your domain

Own the name. Point it to your site.

By the end of this module

Connect a domain while preserving existing services.

A registrar sells and renews your domain. DNS tells browsers and other tools where its services live. Cloudflare can handle both jobs, or only DNS.

Keep the Netlify URL for your first test. For an existing domain, record the whole DNS zone before changing entries. MX supports incoming email. TXT may hold SPF, DKIM, DMARC and ownership checks. Subdomains may host other applications.

You can stop this exercise here if you have no domain. Your site is already online.

Your turn

  1. Add your domain in Netlify → Domain management → Add a domain you already own. Read the DNS instructions for this project.
  2. If Cloudflare already manages DNS, open DNS → Records. For a new zone, import and verify existing records before changing nameservers at the registrar. Avoid conflicting DNS providers.
  3. For a Cloudflare zone, create the root entry requested by Netlify. It may recommend a flattened CNAME to apex-loadbalancer.netlify.com. Point www to your project’s .netlify.app hostname. Start with DNS only so Netlify handles HTTPS directly.
  4. Preserve email and subdomain records. If a web entry already exists or an MX depends on the root domain, resolve that dependency before switching.
  5. Allow time for propagation. Check DNS and the certificate in Netlify. Open both the bare domain and www, and confirm the redirect to the primary domain.

What free plans allow

Cloudflare offers free DNS. The domain itself has a purchase and renewal cost that depends on its extension and registrar.

When to pay, and why

The normal cost at this point is the domain. A paid Cloudflare plan addresses additional protection, performance or support needs. Check specific features before buying.

Watch out for this

An HTTPS padlock protects the connection. It does not prove the site is honest or bug-free. Never bypass a certificate warning.

Your exercise

Record the domain’s renewal date. Check HTTPS and www in a private window.

Check your understanding · Which DNS record needs special care to preserve incoming email?

Next module
Official sources
07

Free plans, paid plans and limits

Pay for a need. Measure it first.

By the end of this module

Make a practical budget and finish your launch.

Plans checked on 17 November 2026. Prices and quotas change. Your billing dashboard and official plan page determine what applies to your account, especially on a legacy plan.

On current Netlify credit-based plans, Free includes 300 credits a month. Production deployments, traffic and some processing share that budget. Older accounts may use a different billing model.

ChatGPT or Claude can help you build within free-plan limits. A chat subscription does not automatically fund the API calls made by a website.

This exercise’s stack publishes pages. A contact form needs a tested receiving service. Payments, accounts, user files and sensitive data need additional design. Adding a button does not create those services.

Your turn

  1. Open Netlify Usage & billing. Find your plan, billing period, usage categories and what happens at the limit. Enable available alerts.
  2. Before paying, write down the problem. For example, “traffic approaches my quota every month” or “we need to work as a team”. Compare plans against that need.
  3. Separate annual domain costs, hosting, the AI creation assistant and any APIs in your budget. Check currency, taxes and automatic top-up settings.
  4. Run your final review. Test with a keyboard and phone, remove fictional content and check your links. If you add a form later, confirm that an actual submission arrives.

What free plans allow

Learning and publishing a small static site can start free. A custom domain adds a recurring cost. Free tiers have usage and feature limits.

When to pay, and why

Real usage or a required feature should drive an upgrade. Reduce oversized images and unnecessary production deployments before increasing your bill.

Watch out for this

Visitor capacity depends on page sizes, requests and functions. There is no fixed free visitor count guaranteed in this course.

Your exercise

Write a budget and finish the sentence “I will upgrade if…”. Ask one person to review your live URL.

Check your understanding · When should you consider a paid plan?

Official sources

Useful words

Build
Preparing publishable files from source code. Our HTML exercise needs no build.
Deployment
Publishing a version of a website.
DNS
Records that connect a name to its services.
HTTPS
An encrypted connection between a browser and a website.
API
An interface that lets software call another service.

Content and plans checked on 17 November 2026. Consult official sources for current terms.