- Update copyright. - Remove manifest.in since we're switching to PDM (and defaults moved to the module). - Remove setup.py since we're switching to PDM. - Remove chains.yaml, move data to the processor module. - Fix passthrough in __main__ - Move main function to separate function to support PDM entrypoint. - metadata.py: Extensive rework * Add heck support (lots of little changes to support it). (.heck files can replace .meta files) * Add yaml metadata support (.meta files can be yaml) * Some formatting changes. * Make metatree be a little easier to read by separating out functionality into extra functions - processchain.py: Move chains.yaml to a structure internal. - Add processors/process_heck.py to support the document side of HECKformat - add pyproject.toml and embrace PDM.
26 lines
1.4 KiB
Markdown
26 lines
1.4 KiB
Markdown
# 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.
|
|
|
|
|