From a0ff225ce37474a40844e7076535441a58bfd71b Mon Sep 17 00:00:00 2001 From: Marty Sluijtman Date: Thu, 18 Aug 2022 15:30:54 +0200 Subject: [PATCH] typo --- content/rambles/hugo.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rambles/hugo.md b/content/rambles/hugo.md index 721e27e..a8d432c 100644 --- a/content/rambles/hugo.md +++ b/content/rambles/hugo.md @@ -34,11 +34,11 @@ This time really diving into the structure of the themes and it clicked. A thing that probably helped this time around was that it very quickly became clear to me that the features I had been half arsedly implementing in my Makefile were standard features for Hugo. Another thing that undoubtedly helped being that the philosophy and syntax of Pandoc's more advanced features are quite similar to Hugo's. -# Disservice to Hugo +## Disservice to Hugo One big thing I bump into with Hugo is the fact that most Hugo websites I come across take one template and _maybe_ change the colorscheme. I feel this is a great disservice to the potential that Hugo has to offer in terms of flexibility. -Yes, you _can_ have it similar to Wordpress, but you don't _have to_. +Yes, you _can_ have it act similar to Wordpress, but you don't _have to_. I was scared off because I assumed would have to use some existing template or get my CSS to work within a Hugo context. The process of which, I assumed, would be mostly having beat Hugo into submission before it would display the things I wanted in the way I wanted.