HUGO - Build A Website With Total Control
As some of you may have realized, this site is powered by HUGO. :P
If (like me) you prefer to use super-fast command line tools instead of bloated WYSIWYG crapware, then give HUGO a try. Heck, you can even host a free blog just like this on Github and run it all inside your account there if you dont want to self host like I am.
This is going to be all for a while from me, as I really have to get back to focusing on my PWK Course in readiness for the OSCP Exam.
Read on and you too can bask in the joys of rapid static html deploymentses and superfasts page loadingseses…
Step 1. Install Hugo
Go to hugo releases and download the appropriate version for your os and architecture.
Save it somewhere specific as we will be using it in the next step.
More complete instructions are available at installing hugo
Step 2. Build the Docs
Hugo has its own example site which happens to also be the documentation site you are reading right now.
Follow the following steps:
- Clone the hugo repository
- Go into the repo
- Run hugo in server mode and build the docs
- Open your browser to http://localhost:1313
Corresponding pseudo commands:
git clone https://github.com/spf13/hugo cd hugo /path/to/where/you/installed/hugo server --source=./docs > 29 pages created > 0 tags index created > in 27 ms > Web Server is available at http://localhost:1313 > Press ctrl+c to stop
Once you’ve gotten here, follow along the rest of this page on your local build.
Step 3. Change the docs site
Stop the Hugo process by hitting ctrl+c.
Now we are going to run hugo again, but this time with hugo in watch mode.
/path/to/hugo/from/step/1/hugo server --source=./docs --watch > 29 pages created > 0 tags index created > in 27 ms > Web Server is available at http://localhost:1313 > Watching for changes in /Users/spf13/Code/hugo/docs/content > Press ctrl+c to stop
Open your favorite editor and change one of the source content pages. How about changing this very file to fix the typo. How about changing this very file to fix the typo.
Content files are found in
docs/content/. Unless otherwise specified, files
are located at the same relative location as the url, in our case
Change and save this file.. Notice what happened in your terminal.
> Change detected, rebuilding site > 29 pages created > 0 tags index created > in 26 ms
Refresh the browser and observe that the typo is now fixed.
Notice how quick that was. Try to refresh the site before it’s finished building.. I double dare you. Having nearly instant feedback enables you to have your creativity flow without waiting for long builds.
Step 4. Have fun
The best way to learn something is to hack with it.