Skip to content

Latest commit

 

History

History
209 lines (135 loc) · 6.92 KB

TODO.md

File metadata and controls

209 lines (135 loc) · 6.92 KB

Todo

Build system

  • Support specifying plantuml common configuration file.

  • Support specifying plantuml include search path.

  • A system of tag in yaml metadata allowing to build only part of the files.

    This would be useful in particular for building only part of the wiki meant for a particular audience (public, work, such or such group, etc).

    In directory dot yaml file would allow to add or remove tags to all document beneat this directory as if had been provided directly in the file's front matter (thus allowing a concept of private / public by default).

    A +@tag -@tag and @tag could be used (how about # tag instead of @ ones?).

    Going even further, it would even be possible to tag sections of the files (i.e: a tag in the title would mean the whole section and its sub).

    Going again even further, pandoc native divs could be used to to tag arbitrary parts of the document.

    A filter would be responsible for processing the tags, maybe generating a custom make file.

    Some remaining questions:

    • Name of the dot file.
    • Kind of tag used.
    • How to tag non md files individually (via dot file?).

    A first draft for the file, would be to specify all the files using the --metadata-file=FILE starting from the root to the page (multiple can be specified).

    Here are some ref to use of a similar tag system:

  • Alternative build system

    Possibly: shake, scons, etc.

    • Supporting spaces in file paths.

  • Experiment with finding a good default ordering for pages when outputting to a linear document (e.g.: pdf, docx, epub) via a lua filter that would create a tree of link.

  • Opt-in for pancritic / CriticMarkup

  • A build target that uses pandiff to output a CriticMarkup annotated document (docx) or set of documents (html / md).

    This would be usefull to express deltas in between two revisions, and share those with others.

  • A dot pmw configuration to control automatic attributes assignment to code blocks or code inlines.

    This can be specified wiki whole, per directory (see above system), per file and even eventually via native div elements (for everything under the div).

    Some use cases:

    • Specifying the default language for code blocks and inlines.

  • A convention for links to code symbol

    See / follow the following discussions:

    Interesting conventions:

    [`My.Symbol`]

  • Sphinx doc indexed symbols integration.

    When inline code symbol is found in the index, make the inline code a link to the symbol's documentation page. A filter should be reponsible for this integration.

    We could make this configurable based on the inline's attributes (link to one or the other sphinx doc based on langage, or explicitly).

    A dot pmw configuration can be used to configure the location of sphinx doc and how inlines are treated by default, what condition make it use one db or the other, or none.

  • Doxygen doc indexed symbols integration.

    Same design as above.

Gnumake

  • Support graphviz dot files.

  • Support haskell diagrams.

  • Build to linear pdf / docx

    Requiring user provided listing of files.

    Most likely through a well known yaml dot file in the sources of the wiki.

    Alternatively, it might be better to simply make those from *.md files making use of the @import directive to compose the final documents. Nice things with this approach:

    • In editor html preview of the resulting document.
    • Granular control over how the document is transcluded.
    • Can surround the transclusions with actual content.

    We could also decide to reuse the pandoc template format. Not sure tough if that can be of any use for the docx like binary formats.

  • A target that prints the html output root directory.

  • A target that prints the wiki root directory.

Html

  • Error on nonexistent image links.

    See Features/LinkSupport/Home

  • Add tarball / zip targets of the html content.

  • Add opt-out option of in output generated files:

    Encoded as a set of potentially overridable template files (using mustaches?) under .html/generated.

    • Convenience Makefile which would have the all, clean, tarball, zip and individual file targets simply deferring to the original makefile.

    • shell.nix / .envrc allowing users to use the make file.

      When companion source repo is found beside this one, its shell.nix would be used.

      Otherwise, When generated, the current git sha1 of the source repo would be taken allowing shell.nix to function without the companion source repo but also for reproducibility.

    • Readme.md describing how to build this output, referencing to source repository, describing exactly how it was generated (source revision / clean or unclean) and could be generated again.

  • clean-html -> Remove directory when empty.

Filters

  • A filter that fails on broken link (input)
  • A filter that fails on broken link (output)
  • Inline dot support.
  • Inline haskell diagrams.
  • Inline vega / vega-lite diagram.
  • Code chunk support filter
  • TikZ support.
  • Vega support.
  • Add support for pandoc-plot

puml-cb-to-img.lua

  • Capture image related attributes and forward others to the image element.
  • Support force render as code block (code_block=true).
  • Support build system specified plantuml common configuration file.

imports-to-link.lua

  • Support graphviz dot files.

  • Support haskell diagrams.

  • Support importing another markdown page.

  • Support importing common images formats.

  • Support erd diagrams (selective code chunk).

  • Support importing pdf files.

  • Support force render as code block (code_block=true).

  • Support file as code chunk.

    Should need a by default mecanism that allow for a chunk-wise accept to prevent arbitrary code to endanger a machine.

    A set of trusted uri can be used too to prevent too much verbosity.