As I've been writing, I've collected posts about specific projects into series through Hugo's [taxonomies](https://gohugo.io/content-management/taxonomies/). The example I've been working on is my [Blogging with Quartz](https://blog.ndumas.com/series/blogging-with-quartz/) series.
As I've been writing, I've collected posts about specific projects into series through Hugo's [taxonomies](https://gohugo.io/content-management/taxonomies/). The example I've been working on is my [Blogging with Quartz](/series/blogging-with-quartz/) series.
## Why does it work?
## Why does it work?
Taxonomies are great, you can even assign multiple taxonomies to a single page when that's relevant ( making a movie database or something, I suppose ?).
Taxonomies are great, you can even assign multiple taxonomies to a single page when that's relevant ( making a movie database or something, I suppose ?).
## Why doesn't it work?
## Why doesn't it work?
The base implementation in Quartz is pretty bare though. The term listing lists the name and the members of the taxonomy, which is great but only goes so far. I'd love to be able to write an overview of each series and have the option of embedding media.
The base implementation in Quartz is pretty bare though. The term listing lists the name and the members of the taxonomy, which is great but only goes so far. I'd love to be able to write an overview of each series and have the option of embedding media.
## What are the options?
## What are the options?
Hugo's Taxonomies feature is prepared for this, but Quartz's templates were not.
Hugo's Taxonomies feature is prepared for this, but Quartz's templates were not.
There were two tricky things about this.
There were two tricky things about this.
### Where does it go?
### Where does it go?
I chased a few weeks worth of red herrings here, so I'll cut to the chase.
I chased a few weeks worth of red herrings here, so I'll cut to the chase.
Taxonomies contain terms. Taxonomies are content. This means my task was pretty simple:
Taxonomies contain terms. Taxonomies are content. This means my task was pretty simple:
```
```
content/
content/
notes/
notes/
series/
series/
blogging-with-quartz/
blogging-with-quartz/
_index.md
_index.md
@ -113,7 +113,7 @@ The final template looks like this.
</html>
</html>
```
```
## Now what?
## Now what?
We've got a nice looking series page now:
We've got a nice looking series page now:
{{<figure
{{<figure
@ -122,4 +122,4 @@ We've got a nice looking series page now:
caption=""
caption=""
>}}
>}}
The next steps are to start filling out my series pages and writing about my projects. This actually clears out the outstanding list of projects I had for the blog, so I don't have any big structural stuff to do.
The next steps are to start filling out my series pages and writing about my projects. This actually clears out the outstanding list of projects I had for the blog, so I don't have any big structural stuff to do.
Too many times this year I've found myself struggling to improve my [blog pipeline](https://blog.ndumas.com/series/blogging-with-quartz/) because I couldn't keep track of when code stopped and started doing what it was supposed to do. This was entirely my own fault, I was not observing best-practices:
Too many times this year I've found myself struggling to improve my [blog pipeline](/series/blogging-with-quartz/) because I couldn't keep track of when code stopped and started doing what it was supposed to do. This was entirely my own fault, I was not observing best-practices:
{{<lead>}} Life is complicated. Your notes don't have to be.{{</lead>}}
{{<lead>}} Life is complicated. Your notes don't have to be.{{</lead>}}
## Why should you trust me?
## Why should you trust me?
I've got [~20 years experience](/resume.pdf) in software engineering and system administration, roles which call for attention to detail, the ability to recall and synthesize information in novel ways, as well as identifying problems and breaking them down into specific actionable goals. Effective note-taking is much the same: [notes are tools](https://blog.ndumas.com/2024/09/notes-as-tools) that you create to make some part of your life better. Sometimes the problems they solve are foreseen and sometimes they surprise you.
I've got [~20 years experience](/resume.pdf) in software engineering and system administration, roles which call for attention to detail, the ability to recall and synthesize information in novel ways, as well as identifying problems and breaking them down into specific actionable goals. Effective note-taking is much the same: [notes are tools](/2024/09/notes-as-tools) that you create to make some part of your life better. Sometimes the problems they solve are foreseen and sometimes they surprise you.
Effective software and effective note-taking systems both combine interactive human input with "stored" data to offer a solution to some problem in a person or organization's life.
Effective software and effective note-taking systems both combine interactive human input with "stored" data to offer a solution to some problem in a person or organization's life.