Set tags as the next project to work on

d3f44bb0573aac1f11ef70339a6d5449c2c55c96

Tucker McKnight <tucker@pangolin.lan> | Mon Feb 02 2026

Set tags as the next project to work on

Also mark a task done that I didn't mark as done before, about
merge commits not showing up in the commit log. (f0856f6c)
wiki/index.md:12
Before
11
12
13
14
15
16
17
18
19



20
21

## Works in Progress


## Ideas and Todos

- [ ] Tag snapshots
  - Goal: have HTML pages generated for user-specified tags in the repo, not
    just each branch head.
⁣
⁣
⁣
- [ ] Create links consistently with some kind of nav or link helper
  - Goal: Links to various pages are being manually created with a hodgepodge
    of splitting and slugifying strings. Create an easy and consistent way for
After
11
12
13



14
15
16
17
18
19
20
21

## Works in Progress

⁣
⁣
⁣
- [ ] Tag snapshots
  - Goal: have HTML pages generated for user-specified tags in the repo, not
    just each branch head.

## Ideas and Todos

- [ ] Create links consistently with some kind of nav or link helper
  - Goal: Links to various pages are being manually created with a hodgepodge
    of splitting and slugifying strings. Create an easy and consistent way for
wiki/index.md:34
Before
33
34
35
36
37
38
39
    created as part of the site generation.
  - Maybe allow `copyTo` to have variable interpolation in it, for totally
    custom directory paths
- [ ] Make merged commits show up in the commits list and commit page.
  - These don't show up as anything right now
- [ ] Create shortcodes that allow 11ty blog posts to reference commits
  - Seems like this could work well for embedding code (specifying line ranges?) in
    blog posts.
After
33
34
35


36
37
    created as part of the site generation.
  - Maybe allow `copyTo` to have variable interpolation in it, for totally
    custom directory paths
⁣
⁣
- [ ] Create shortcodes that allow 11ty blog posts to reference commits
  - Seems like this could work well for embedding code (specifying line ranges?) in
    blog posts.
wiki/index.md:68
Before
67
68
69


70
71
  - add a Dockerfile for node 18, which is the lowest 11ty supports, and see if
    this is useable on that.
  - lodash is one of the larger (largest?) dependencies right now. With mithril auto-escaping strings, it might not be necessary anymore. Look into which things actually need to be escaped (e.g. any user-input from commit messages) and see if we can just rely on mithril to escape those
⁣
⁣
- [x] Better Template Readability
  - git-branch: `mithril-server-side-rendering`
  - Goal: Do not simply have a bunch of strings as the HTML for the default virtual
After
67
68
69
70
71
72
73
  - add a Dockerfile for node 18, which is the lowest 11ty supports, and see if
    this is useable on that.
  - lodash is one of the larger (largest?) dependencies right now. With mithril auto-escaping strings, it might not be necessary anymore. Look into which things actually need to be escaped (e.g. any user-input from commit messages) and see if we can just rely on mithril to escape those
- [x] Make merged commits show up in the commits list and commit page.
  - These don't show up as anything right now
- [x] Better Template Readability
  - git-branch: `mithril-server-side-rendering`
  - Goal: Do not simply have a bunch of strings as the HTML for the default virtual