# Does ht-include allow for recursion?

**URL:** <https://hypertexting.community/t/does-ht-include-allow-for-recursion/61>\
**Category:** HyperTemplates\
**Created:** [June 18, 2025, 3:34pm UTC](https://hypertexting.community/t/does-ht-include-allow-for-recursion/61 "2025-06-18T15:34:17Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![calebhailey.com](https://yyz2.discourse-cdn.com/flex036/user_avatar/hypertexting.community/calebhailey.com/32/18_2.png) [@calebhailey.com](https://hypertexting.community/u/calebhailey.com)\
**Post date:** [July 3, 2025, 9:50pm UTC](https://hypertexting.community/t/does-ht-include-allow-for-recursion/61/21 "2025-07-03T21:50:05Z")

</div>

> [@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.

---

<div class="post-metadata">

**Author:** ![calebhailey.com](https://yyz2.discourse-cdn.com/flex036/user_avatar/hypertexting.community/calebhailey.com/32/18_2.png) [@calebhailey.com](https://hypertexting.community/u/calebhailey.com)\
**Post date:** [July 9, 2025, 5:55pm UTC](https://hypertexting.community/t/does-ht-include-allow-for-recursion/61/22 "2025-07-09T17:55:54Z")

</div>

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`](https://hypertemplates.net/docs/reference/cli/commands/build/), [`hyperctl deploy`](https://hypertemplates.net/docs/reference/cli/commands/deploy/), [`hyperctl generate`](https://hypertemplates.net/docs/reference/cli/commands/generate/), and [`hyperctl publish`](https://hypertemplates.net/docs/reference/cli/commands/publish/).

---

<div class="post-metadata">

**Author:** ![AtmanActive](https://yyz2.discourse-cdn.com/flex036/user_avatar/hypertexting.community/atmanactive/32/55_2.png) [@AtmanActive](https://hypertexting.community/u/AtmanActive)\
**Post date:** [July 9, 2025, 6:51pm UTC](https://hypertexting.community/t/does-ht-include-allow-for-recursion/61/23 "2025-07-09T18:51:59Z")

</div>

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.

[Previous page](https://hypertexting.community/t/does-ht-include-allow-for-recursion/61.md?page=1)