This is the second post of a series where I want to give some tips and tricks for the Terminal/CLI.
In the first post, I showed a few very handy tools like bat, exa, multitail, diff-so-fancy, delta, prettyping and htop/gtop/vtop.
This post is going to be a little longer so buckle-up, put your helmet on, grab a … frying pan and have fun.
This is the first post of a series where I want to give tips and trick for the Terminal/CLI, have fun:
bat and catexa and lsmultitail and taildiff-so-fancy, delta and git diffprettyping and pinghtop/gtop/vtop and topThis is the third post of a series, you might want to check the previous articles: (Intro and Content) before reading this.
Since we only have static files, we only need a simple web server to serve the site. It can be self-hosted or hosted on a cheap Webhosting solution and there are other cool options, like:
This is the second post of a series, you might want to check the first article (Intro) before reading this.
Hugo is very flexible in terms of configuration and organizing the content, you have a lot of options and you can do things in various ways. This might sound great but if you ask me, I rather like opinionated things where I don’t need to put a bunch of effort in figuring out best practices but the framework gives those to me (Convention over Configuration™). Unfortunately, this is not the case for Hugo.
The whole thing started with: “I think I want to create a blog”. I had a few ones before, those were either all-in-one hosted solutions or self-installed WordPress sites. WordPress was a tempting pick this time (as always) but I’ve played a little with Jekyll and Hugo recently and I liked them. So I negligently threw the red button with the text “Deploy WordPress” back to the shelf and I brought up a little toolbox that has the text JAM Stack on it from my shed (not bikeshed), also I liked the idea of hosting the blog on GitHub Pages.