Publish Your Website: Static Hosting, GitHub Pages, Netlify, Custom Domains, DNS Records and HTTPS Step by Step

Web Designing 55 min min read Updated: Nov 17, 2026 Intermediate
Publish Your Website: Static Hosting, GitHub Pages, Netlify, Custom Domains, DNS Records and HTTPS Step by Step
Intermediate Topic 2 of 3

Static vs Dynamic Sites

Static siteDynamic site
FilesReady HTML, CSS, JavaScript, imagesPages built by a server for each visit
ExamplesPortfolio, landing page, documentationShop, social network, booking system
HostingSimple and often freeNeeds server, database and more setup

This course focuses on static sites, which is the best place to start.

Where to Host

OptionNotes
GitHub PagesFree hosting from a GitHub repository for static sites
Netlify, Vercel, Cloudflare PagesConnect a Git repository and they build and deploy on every push
Shared or cloud hostingUpload files with FTP or a control panel
Check current plans Free plans, limits and screens change over time. Read the host's current documentation before you depend on a feature.

Deploy with GitHub Pages (Outline)

  1. Push your project to a GitHub repository with index.html at the root
  2. Open the repository Settings, then Pages
  3. Choose the branch and folder to publish
  4. Wait a minute and open the address shown (it looks like username.github.io/repo-name)
  5. Fix paths if CSS or images do not load (use relative paths such as css/style.css)

Deploy with a Git-Connected Host (Outline)

  1. Sign in and choose Add new site, Import from Git
  2. Select your repository
  3. If your site has no build step, leave build empty and set the publish folder to the project root
  4. Click Deploy
  5. Every push to main now redeploys automatically

Custom Domain

  1. Buy a domain from a registrar
  2. In your host, add the custom domain
  3. In the registrar's DNS settings, add the records the host asks for
  4. Wait for DNS to update (minutes to many hours)
  5. Turn on HTTPS (most hosts issue a free certificate automatically)
DNS recordPurposeExample
APoints a name to an IPv4 addressexample.com to 203.0.113.10
AAAAPoints a name to an IPv6 addressexample.com to an IPv6 address
CNAMEPoints a name to another namewww.example.com to username.github.io
TXTText proofs, such as domain verificationA verification code
MXWhere email for the domain goesMail provider servers
Documentation addresses The example IP address above is from a reserved documentation range. Always use the exact values your host gives you.

Why HTTPS?

  • Encrypts data between visitor and site
  • Browsers mark HTTP sites as not secure
  • Required for many modern features
  • Helps trust and search visibility

Post-Launch Checklist

  1. Open the site on phone and laptop
  2. Test every link, form and image
  3. Check that http:// redirects to https:// and www to the main name
  4. Test the 404 page
  5. Run Lighthouse
  6. Submit the sitemap to Search Console
  7. Set up analytics (with consent where needed)
  8. Create a backup plan

Practice

  1. Publish your practice site with GitHub Pages or a similar host
  2. Add a custom domain if you own one
  3. Run the post-launch checklist

Conclusion

A static site is easy to publish: push your files, let a host deploy them, add a domain and DNS records, turn on HTTPS and run a launch checklist.

Quick Summary: Static vs dynamic; hosts; GitHub Pages; Git-connected; domain; DNS; HTTPS; checklist.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators