Skip to content

Commit 63e0d77

Browse files
committed
Publish first part of making-this-site
1 parent e0b4378 commit 63e0d77

1 file changed

Lines changed: 5 additions & 2 deletions

File tree

content/posts/making-this-site.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
+++
22
title = 'Making This Website'
33
date = 2026-02-10T13:33:00-05:00
4-
draft = true
4+
draft = false
55
tags = ['hugo', 'tutorial']
66
+++
77
# How did you make this website?
@@ -10,9 +10,9 @@ It was simple, really. I used ***Hugo*** and ***GitHub Pages***. (Along with som
1010
## Making the website
1111
The first step, in my opinion, should be to build the website itself. There's no sense in worrying yourself about hosting options and infrastructure before you've even created a presentable website to host. A simple portfolio/blog site such as this is called a *static* site, meaning that there are no underlying databases or other backend functionality. That's not to say that the website can't be made interactive with JavaScript, CSS animations, etc., but there is no work being done on the server's part when a user interacts with the website.
1212

13-
### Installation
1413
The easiest way to create a static site is to use a *static site generator* (SSG). There are many of these available, but the most popular are **Hugo** and **Jekyll**. Both function very similarly, and are supported by basically every hosting platform. Jekyll is generally considered to be more compatible with GitHub Pages than Hugo, but I didn't find this to be the case in my own testing. There are many Jekyll themes that are **not** compatible with GitHub Pages, whereas just about any Hugo theme can be made compatible using free GitHub Actions workflows. For this reason, I decided to create this website using ***Hugo*** over Jekyll, but many of the steps in this guide could be used with Jekyll as well.
1514

15+
### Installation
1616
In order to begin working with Hugo, you need to install it onto your device. It should be fully compatible with Windows, Linux, BSD, and MacOS. Although, if you're using Windows, I'd recommend installing [Windows Subsystem for Linux](https://learn.microsoft.com/en-us/windows/wsl/install) first since Linux is generally more predictable than Windows, and will make following this guide a lot easier. If you have some kind of limited operating system like a Chromebook or mobile device, things are a little trickier, but you should be able to simply skip ahead to the setup of GitHub pages and then do all of your development directly on GitHub, rather than installing anything locally. To install Hugo, you'll need to install both the Hugo program and Git onto your device. Git is the program we'll be using to install themes, keep track of changes to our site, and publish them to GitHub. You can install git from the [git website](https://git-scm.com/install/), then Hugo from the [Hugo website](https://gohugo.io/installation/) by scrolling down to the "Package Managers" section for your operating system. Windows users using WSL should follow the Linux instructions for Debian.
1717

1818
### Creating a site
@@ -62,3 +62,6 @@ Most websites also have what's called a **favicon**, which is the image that app
6262

6363
### Done!
6464
We now have a complete website on our computer with all of the content we want to include! With this done, it's important to perform another `git commit -m "Done!"` to save our changes. Once we're publishing our website through GitHub Pages, our published website will only update when we `git commit` our changes, not when we merely save the files.
65+
66+
## Hosting and Publishing
67+
This part of the guide is coming soon! In the meantime, feel free to start looking at registrars for a great domain name.

0 commit comments

Comments
 (0)