To Do's
- current issues:
- All images should link to page with full-size image, but also include attribution info. Maybe FM gallery?
- Front Matter as CMS
-
define FM content types for blog, journal, project
- distinguish FM fields, can bundle, can be sub content
- define templates for each kind (esp project header vs project subcontent)
- bulk edit legacy pages to remove unused FM fields
-
define FM content types for blog, journal, project
-
Image processing:
- use digikam as primary archive, not FM media manager
- Resize content for full size, half column width, maybe mobile (if much different from half column width). Bite the bullet and agree to use pixel widths for now.
- Home page
-
navigate among projects -- drop down menu on home page
accomplishedhacked by putting a manual list under/projects.
-
navigate among projects -- drop down menu on home page
- journal:
- 1 page per month; content is a definition list of daily entries (filename is YM.md). Considered using FM data, but that's hard to edit.
-
View is stream of
... - It would be nice if you could scroll freely across month boundaries.
- blog:
-
[won't do] path is
/<base>/<dategroup>/<uniqueName>/
-
[won't do] path is
- old content (from hugo-blog):
- get images working A: define them all in FM and use its tools.
- page path based on file name (no need for name in FM)
-
get markdown task list (checbox markup
- [ ]) working - projects:
- don't show author, tqgs date line.
- Do show list of chapters as nav on lhs.
- on project landing page, show list of chapters (same lhs?)
- Add first project - care and feeding of the website itself.
- /projects page and list of projects
-
index page is reverse chrono list of items with date g rouping
. Zola features
-
understand 'series' (for chapter books or projects?)
No need for separate taxon, tags is good enough. - understand 'category' vs tags. Use tags a lot, not sure categories means anything.
-
understand 'series' (for chapter books or projects?)
- how to register and enforce tags (CMS function?)
-
section.html doesn't iterate over
section_item.subsection, should do both. - Extract section nav as separate template block, put on lhs.
- lhs should be sticky column, but responsive.
- lhs should not be squeezed when content is a big page.