Transforms?

[s3ththompson]

Would you be open to a rewrite of nanocontent that supported arbitrary transforms (similar to sheetify)?

Feature requests such as #10 suggest that there are diverging needs between nanocontent as an in-browser content wrangler and a static site generator. Transforms could help keep the core of nanocontent simple and well-tested while encouraging others to add custom functionality on their own via custom transforms.

(Additionally, adding a custom parser is currently incompatible with using nanocontent/transform.) WDYT? (cc @jongacnik)

[s3ththompson]

Two other use cases:

• swapping out a heavy-duty Markdown parser
• generating custom image sizes for something like monoimage