unified-projects

meta-repo for contributions to the unnifedjs community

Projects:

Remark plugins

• remark-content-separation-flags
  • apply the unist-util-slice to the md(x)ast for remark usage
• remark-mermaid-plugin-inline
  • process the mermaid code blocks in remark content
• remark-configure-nudge-cmment
  • add a node to the frontmatter or comment to the top of prose letting future MD readers know that the content requires a specific plugin composition so that the content can be rendered.

Rehype plugins

• rehype-content-separation-flags
  • apply the unist-util-slice to the hast for rehype usage

Unist-utils

• unist-utill-slice
  • chops up a unist node/tree into non-overlapping slices based on designated separator nodes
• unist-util-chunk
  • process a unist node/tree into possibly overlapping segments based on designated start/stop nodes

Utils for Plugin Developers

• vfile-create-effects
  • util that allows plugin authors to emit new data that models side effects that still needing to be processed
• vfile-handle-effects
  • a batteries inluded plugin that installs and uses all the following default vfile-handle-effects-* functions.
• vfile-handle-effects-fs
  • util that allows plugin authors to emit new data that models side effects that still needing to be processed - where the data represents files to be written to the fs.
• vfile-handle-effects-http
  • util that allows plugin authors to emit new data that models side effects that still needing to be processed - where the data is an http call needing to be requested.
• vfile-handle-effects-socket
  • util that allows plugin authors to emit new data that models side effects that still needing to be processed - where the data is a message to drop on a socket/websocket/zeromq connection etc. [FUTURE]
• vfile-handle-effects-dom
  • util that allows plugin authors to emit new data that models side effects that still needing to be processed - where the effect is a virtual-DOM tree needing to be applied at some tree location. [FUTURE]
• vfile-subscriptions
  • [FUTURE Project] vfile effects could then be used as inputs for other plugins and effects

Templast Ecosystem (All work in progress)

• templast

Handlebars Support

• templast-hbs-parse parse handlebars templates
• templast-hbs-verify parse handlebars templates // TASTY --> HBS dialect
• templast-hbs-stringify parse handlebars templates --> HBS Dialect --> string

mustache Support

• templast-mustache-parse
• templast-mustache-verify assigns warnings or failures to the template if the source file was from some other template system and is now going to be rendered as a mustache file.
• templast-mustache-stringify

doT Support

• templast-doT-parse incorporate doT templates into templast
• templast-doT-verify incorporate doT templates into templast
• templast-doT-stringify incorporate doT templates into templast

apacheVTL Support

• templast-apacheVTL-parse incorporate apacheVTL templates into templast
• templast-apacheVTL-verify incorporate apacheVTL templates into templast
• templast-apacheVTL-stringify incorporate apacheVTL templates into templast

js Tempalte Literals

• templast-jsTemplateLiterals-parse incorporate jsTemplateLiterals into templast
• templast-verify-jsTemplateLiterals incorporate jsTemplateLiterals into templast
• templast-jsTemplateLiterals-stringify incorporate jsTemplateLiterals into templast

EJS Support

• templast-ejs-parse incorporate apacheVTL templates into templast
• templast-ejs-verify incorporate apacheVTL templates into templast
• templast-ejs-stringify incorporate apacheVTL templates into templast

EJS Support

• templast-ejs-parse incorporate apacheVTL templates into templast
• templast-ejs-verify incorporate apacheVTL templates into templast
• templast-ejs-stringify incorporate apacheVTL templates into templast

JADE Support

• templast-ejs-parse incorporate apacheVTL templates into templast
• templast-ejs-verify incorporate apacheVTL templates into templast
• templast-ejs-stringify incorporate apacheVTL templates into templast

Roadmap

• type-system guarentees
• help needed for jade
• help needed for pug
• subset of EJS
• subset of ERB
• explore supporting some subset of "PHP templates"

Usage

npm start will download a ton of other git repos into the packages folder. Where each of the packages have their own repo and lifecycle.

Then use the npx meta command to manage all those sub-repos in some type of lerna-overlord-style

PIPEDREAMS

• to-and-fro-Apache-Velocity-Templates

  • Parse VTL to unist
  • Parse mustache to unist
  • Parse mustache to unist
  • VTL to mustache ?? https://mustache.github.io/mustache.5.html?
    • hash lookups
    • hash context windows - and subsequent attribute lookups
    • comments
    • partials
  • VTL to handlebars
    • hash lookups
    • hash context windows - and subsequent attribute lookups
    • HTML escaping
    • block expressions
    • consider it a foreach
      • Sets context to a list and allows attributes to be read for each item
    • nested attr.path
    • context stack can be traversed upward
    • comments
    • helpers can be registered
      • built in #with and #each
    • partials
  • TemplateAST
    • Mustache
    • Handlebars
    • Apache VTL
    • JS Template Strings
    • doT
    • EJS
    • Pug
    • Marko?
    • Jade
  • VTL to MDX?
  • mustache to VTL
  • handlebars to VTL

• Babel7Ast-to-mdxast

  • ref: https://github.com/babel/babel/blob/master/packages/babel-parser/ast/spec.md

• TSast-to-mdxast

• MDXAST

  • MDAST +

  • JSX -> script

  • COMMENT

  • Import

  • Export

• MDXHAST

  • HAST + type: element tagName: div, span, form, input, properties: {} children:[] ƒ h(tagType, {props}, [ children ] )

  • imports

  • exports

  • inlineCode

means that an .mdx file is really a fancy JS file a certain type of JS file that has some convention allowing it to be rendered when invoked with proper context