After a break of 5 days, I decided I had have enough time to adjust to the idea of semantics in HTML. After doing layout and responsive design, I funnily stopped at HTML Semantics. I can see there are schools of thought in web design, not just one agreed upon way of doing things. Interesting…
👨💻🎓🕸🏗
This time I got really stuck in the W3School HTML tutorial at HTML Layout. I had never heard of this facility in HTML before; it must have blown designers' minds when it first popped up. I suppose I need to take my time and read further background information on this subject. It seems daunting, yet necessary to understand before continuing.
👨💻🎓🕸🏗
In the HTML tutorial on W3Schools I've progressed to Iframes. I noticed that many of the things I learned recently just went poof, and I had to search for the correct element name. With that in mind, I'm progressing steadily towards the end of the course/tutorial.
👨💻🎓🕸🏗
I'm slowly progressing through the HTML tutorial on W3Schools. It's a bit boring, because I don't see any application for my acquired knowledge, like a pet project. This probably means most of it won't stick, and I will have to look it up as I need it later.
I stopped at HTML Block & Inline, roughly at a quarter of the entire tutorial.
👨💻🎓🕸🏗
Progress with the Learn HTML course on W3Schools is a lot slower now I'm getting at HTML elements I'm not or less familiar with. Some have changed or been extended with new attributes. I know I can't rush this, or I'll forget most of it.
Right now, I've stopped at HTML Tables.
👨💻🎓🕸🏗
I finished the Cloudcannon tutorial, and as usual, it went totally off the rails for me with too advanced stuff. Ah well, it seemingly only was to wet one's appetite to start learning Hugo.
One of the resources to learn more was the Hugo community forum, where a useful tip was given to newbie Hugo site developers:
You are expected to already know how to assemble a static web page, for which you do need some basic knowledge of html, css, command line and text editors. Or how to prepare a space to host your website. The bottom line is, if you are unwilling to invest the time required to learn these things, then Hugo is not for you.
So, after the git tutorials, I suppose next up is a lot of reading, and reading:
👨💻🎓🕸🏗
I did Hugo templating basics and found it was a bit rushed. Next in the Cloudcannon Hugo tutorial was Blogging in Hugo, which was somewhat understandable.
I still have a problem that the homepage doesn't have a navigation menu, while it should. I have no idea why that is. It's probably something with my installation of Hugo on my Raspberry Pi-400. It demonstrates I really have no clue what I'm doing, while the tutorial gives me the false sense that I do.
👨💻🎓🕸🏗
Okay, I'm learning Hugo from this tutorial on Cloudcannon. The concept of partials is a powerful one, as the lesson on Hugo Partials explains. Things starting to make more sense now.
👨💻🎓🕸🏗
The Hugo tutorial on Cloudcannon started easy enough with an installation guide (I could skip) and a brief tutorial on layouts. They're using Syntactic Awesome Style Sheets instead of static css, because it's supposedly more flexible than static css. Other than that, there won't be any use of css, really.
👨💻🎓🕸🏗