Does ht-include allow for recursion?

[calebhailey.com]

@AtmanActive

But, this approach where a comma means || is very new to me. I’m kind of used to comma being a series of sorts. It’s not that I have anything against this, I just think that it needs to be documented and explained to death in many, many examples so that people can grasp (and memorize!) the concept. Otherwise, I’m all for it.
On the other hand, If you are able to change comma , for OR || in your parser, in this case, that would make it even better/easier.

I’ll have to think on this. I see how the comma might not be super obvious. But I can definitely improve the documentation and add more examples. I’ll keep that in mind.

[calebhailey.com]

Getting ready to publish 0.17.0. I ended up adding four new command flags to all the subcommands that perform builds: hyperctl build, hyperctl deploy, hyperctl generate, and hyperctl publish.

The new command flags are:

1. --content-dir
   Relative path to the content directory to use for the build (overwrites site.config.content_dir). (env: HYPER_CONTENT_DIR)
2. --data-dir
   Relative path to the data directory to use for the build (overwrites site.config.data_dir). (env: HYPER_DATA_DIR)
3. --static-dir
   Relative path to the static directory to use for the build (overwrites site.config.static_dir). (env: HYPER_STATIC_DIR)
4. --theme
   Relative path to theme config to use for the build (overwrites site.config.theme). (env: HYPER_THEME)

These allow for multiple versions of a site to be deployed from a single commit.

@AtmanActive what do you think?

EDIT: the documentation pages are already updated: hyperctl build, hyperctl deploy, hyperctl generate, and hyperctl publish.

[AtmanActive]

This is great!

That’s exactly what was missing.

Will start testing it in the following days.

Maybe some of my test projects could be useful as demos/examples/showcases.