Changes to this website
09 Oct 2023Motivation
- Want to use my blog as a public notes
Note for myself as I convert this into a CMS with github issues.
- Merging existing posts with github issues
- Mirror the existing post structure in the github issue
- To do
- Post page for a github issue
- markdown parsing for the github issue body
- working tags for github issue
- github issues showing up in rss feed
- New label on issues to distinguish "draft" or "published"
- Deployment changes: trigger when github issue is updated/created by the repo owner
- vercel has github token env var already?
- setup comments with uterances?
- reactions
- [x] unrelated: upgrade to 11ty 2.0
- markdown rendering tests
- [x] images
- [ ] edits (e.g. label changes) can change publish date - show more visibility on the page?
- [ ] reactions, ability to go back to the issue
- Post page for a github issue
Things I'm confused about in 11ty
- why does "posts.json" have "posts" as a "tags"
- what makes posts a collection? how is that setup?
how things work
- collections
- "posts" is a collection of all posts
- "tagList" is a collection of all tags
- "githubIssues"
- then every tag is it's own collection, e.g. "books"
- special all collection: https://www.11ty.dev/docs/collections/#the-special-all-collection
- issues are data, and cached
references: https://github.com/NickColley/website-from-github-issues
also check against https://github.com/11ty/eleventy-base-blog/blob/main/package.json