Back

@hollie

Here's an example of a content .md file: https://codeberg.org/youronlyone/content/raw/branch/main/snoworld/en-ph/blog/posts/2022/20220920-extraordinary-attorney-woo-and-autism.md

The information between the two sets of +++ are the frontmatter area. +++ refers to #TOML method while --- is #YAML. (I personally prefer the former, as in the example.)

To have categories and tags (a.k.a. "taxonomies") you only have to add:

categories = ["cat1", "cat2"]
tags = ["tag1, "tag2"]

Most themes have "categories" and "tags". If it isn't showing, it the theme probably doesn't support it. In which case, you have to add it manually.

This is where the /layout/ folder comes into play.

Each theme author places their code in different files, depending on how they want to organize their code.

Files in the /layout/_default/ folder will always be used when Hugo generates your site. If, say, baseof.html is not in the theme, Hugo will generate an error.

Files in the /layout/partials/ folder are only used when another file calls it. Say, in the baseof.html file, it calls the file /partials/meta.html.

---

As to making a new post.

My personal method is to copy my template file located in /archetypes/post.md folder, into my /content/ folder, and rename it accordingly.

The automated way is: hugo new (see: https://gohugo.io/commands/hugo_new/ )

This command will copy the appropariate template file (/arghetypes/ folder) into your /content/ folder and rename the new .md file. You can then edit the file's frontmatter and add your content.

After that, you can generate Hugo again, and upload the files.

If you are using, for example, git, you can push it, and let your host (for example, netlify or cloudflare pages), or your server, pull the latest git commit and automatically re-build Hugo. This way, you don't have to re-upload your /public/ directory for every update.

---

There are "headless CMS" (as it is called) which supports Hugo. What they do is they provide some form of CMS style content editing. It's like a GUI for Hugo.

However, these are third-party projects, and unfortunately, I'm not familiar with them (I don't use them).

Headless CMS (a.k.a. frontend) are useful to remove the techie-ness of static-site generators like Hugo.

^_^