AlderconeStudio/heckweasel
0
0
Fork 0
Code Issues 2 Pull Requests Packages Projects Releases Wiki Activity
Files
trunk
heckweasel/TODO.md
Cassowary 690f110bc5 Major cleanup and fixage for new metadata stuff and heckformat 
- Clean up a ton of documentation.
- Make the modules import nicely.
- Add a cool logo to the command line tool
- Make the command-line tool use tqdm
- Make the command line tool load the metadata before processing the
  files in a separate loop.
- Fix error handling in the command-line tool processing loops so they
  work correctly (and jinja errors are more useful)
- Make command-line tool exit non-zero if there were errors.
- Fix load metadata to handle formats and errors better (and return {}
  if it fails)
2024-02-27 21:50:03 -08:00

1.9 KiB
Raw Permalink Blame History

TODO

  • Smart CSS things (fill in the processors)

  • Project global defines, parameters.

  • pre- and post-scripts that will be run from main, either some shipped with heckweasel or project-level.

  • Library of template modules? ATOM et al.

  • Some off the shelf website templates and a template manager.

  • Live refreshing server thing which maps a heckweasel tree into a web server's memory and updates on change.

  • https://github.com/Python-Markdown/markdown/wiki/Third-Party-Extensions

  • add markdown_link_attr_modifier extension

  • add figureAltCaption extension

  • add qrcode extension

  • Add support to define macros or whatever for Jinja, or to include generic stanzas in any output so adding macros won't mean repeatedly including them.

  • It'd be good to generate a dependency tree and only recompile things based on changes, like makefile-like behavior.

  • Fragments which would be blobs of mechanics like rss feed, thumbnail links, etc. They would be virtual files and other changes to processing chains and project contents. python -mheckweasel --fragment=rss,config=foo.meta etc.

  • Run commands as part of processing chains

  • Project level processing chain overrides in the .meta or whatever.

  • Project settings in separate file from .meta that would basically do .meta stuff. Like global meta + config in a top.heck file by default and overridable by a parameter. Maybe a nice default filename that doesn't start with . (whereas .meta or .heck is the current base metadata)

  • Handle the fact that HECKformat metadata is always a list in a more elegent way. We have some hacks in place where scalar values are expected, but if a project mixes metadata formats it gets a bit messy.

  • Provide a database-like interface to the global metadata tree, so that metameta page templates could query the database to assemble indexes and whatnot without looping over the actual files.