Web Development · Beginner level

Beginner level · Module 5: Publishing a Website · Lesson 2 of 3

Hosting, Domains and HTTPS

Publish a static site, understand domains and DNS records, and make sure the site uses HTTPS.

In this lesson you will

  • Deploy a static site to a hosting service
  • Explain domains, DNS records and HTTPS

Key concepts

static hostingdeploy from GitDNS A and CNAME recordsHTTPS certificates

The lesson

A static site — HTML, CSS, JavaScript and images — can be hosted on services such as GitHub Pages, Cloudflare Pages or Netlify, which can rebuild and publish automatically each time you push to the repository.

A domain name such as myorg.org is rented yearly from a registrar. DNS records connect it to the host: an A record points to an IP address and a CNAME record points to another name. Changes can take time to spread.

HTTPS encrypts traffic between the visitor and the site and is expected by browsers and search engines. Modern hosts issue free certificates automatically; always check that the padlock appears and that http redirects to https.

Step by step

  1. Connect the GitHub repository to a static host.
  2. Publish the site and open its URL on a phone.
  3. Push a change and watch the site update.
  4. Review how a custom domain would be connected with DNS records.

Practice activity

Publish the organisation website and write down the steps needed to connect a custom domain.

Expected result: The site is live over HTTPS and the domain steps are correct for the chosen host.

Check your understanding

  1. What does a CNAME record do?

    Show answer

    Points one domain name to another name.

  2. Why is HTTPS important?

    Show answer

    It encrypts traffic and browsers and search engines expect it.

Taught live by an instructor — online or in person. Free course lessons are for self-study and do not lead to a certificate — see registration options.