Block a user
How does/should SiteConfig deal with weird schemas and basic auth?
Add typed config/frontmatter validation (pydantic? custom?)
The config file was refactored by 4351ea8e0d and now conforms to these requirements. It uses custom validation and creates a type annotated dataclass SiteConfig.
Implement log verbosity levels
Site local template overrides
Add opengraph tags for inline link generation
Adapt heading levels to rendering context
Add typed config/frontmatter validation (pydantic? custom?)
Support a new custom markup format
Add snapshot/test feature to help with refactoring
Introduce photo/photo album content type
Deduplicate files referenced by content
Fix inconsistent heading numbers on index pages
Here's one option that can possibly resolve the headings:
Create content cards that aren't separated by headings. I think I like this but I need to research the impact of not having headings…
Fix inconsistent heading numbers on index pages
build should collect metadata for future builds
Add init subcommand to create a new site directory