My upcoming plans with YASS

[AJ-Ianozi]

I haven't done a lot with YASS since taking over aside from some housekeeping items, mostly because YASS is already a very strong product standing on its own. However, I do have some additional items on the horizon. Here are some of those plans.

Move YASS to Alire

I want to allow people to acquire YASS simply with alr get yass. YASS doesn't have any complicated dependencies (aside from libcmark), so once libcmark has been removed, this should be pretty straightforward. Before that, they may need an external library.

Move away from libcmark

One of the first things I would like to do is migrate away from libcmark and move to a completely Ada solution. I'm currently watching the AdaCore/Markdown library, and once it's feature-par with libcmark, that will be my next priority.

yml/toml config parser

This obviously cannot be 1:1 support, but I would like to include a yml/toml parser to automatically parse jekyll _config.yml and _config.toml files, -- including Jekyll base config settings -- for easier migration from Jekyll to YASS.

Stronger plugin support with HAC

Currently YASS has some pretty cool plugin support, allowing you to write your own plugins in any language you want. And this is fine. However, I also want to include HAC with YASS so people without compilers can simply write "scripts" in Ada that are automatically executed by YASS when building the website.

Evaluating templates & Data Files

One thing that Jekyll excels in with Liquid is allowing Datafiles to be read in their templates. I'm looking into ways to utilize something similar so you can load in json or yml files into your generated website.

Summary

These are some things that I've been thinking about, which I may update later. What are your thoughts?