From local files to a live website with GitHub Pages

You don't need a server to share a useful idea. A few HTML files and GitHub Pages are enough to put a technical blog online.

1. Start with a static site

A static website serves files directly: HTML for content, CSS for appearance, and JavaScript for interactions. This makes it a good fit for a personal blog. There's no database to maintain and no application server to keep running.

Keep your homepage named index.html. Put shared styles and scripts alongside it, and use relative links so the site works under a repository path.

my-blog/
  index.html
  blogs.html
  about.html
  style.css
  script.js

2. Push your files to GitHub

Create a repository and upload your website files to its root. If you use Git locally, commit your files and push them to the repository's default branch. Avoid committing credentials, private notes, or configuration secrets: the published files are public.

3. Enable GitHub Pages

In your repository, open Settings → Pages. Select Deploy from a branch, choose the branch containing your files and the root folder, then save. GitHub builds and publishes the site; deployment may take a few minutes.

4. Check the published result

Open the URL shown in Pages settings. Check your navigation, article links, mobile layout, and images. If a file is missing, confirm its name and capitalization match the link exactly.

5. Keep publishing simple

For a small blog, individual HTML pages are easy to understand. As the archive grows, a static site generator can turn Markdown posts into consistent pages. Start with a workflow you enjoy and improve it when you feel the friction.

The goal is a reliable place to share what you learn. Your first post matters more than a complicated publishing stack.

Sample article for this starter blog.