Thanks for the nice ideas, @ElsLommelen!

For now, would you be willing to create an issue for each of your suggestions? For both, I’d like to think a bit more about the best way to implement them so everything stays consistent and well tested. You can reply to my comments below in the issues to provide any extra details.

I have two more suggestions, up to you to decide on adding them (or not):

• when using child documents, it could be helpful to cache them, as it may be time consuming to build all of them each time during development while there are no changes. For now I added this in the yml heading of my template qmd, but it may be more convenient to add it as an argument in autoqmd_generate_children()? Otherwise it seems helpful to add it as a suggestion in the vignette.

Could you clarify what you mean by “now I added this in the yml heading”? A quick copy-paste or link would help. I’ll need to think about how this would work and how it differs from the existing freeze argument. If you have concrete ideas, feel free to share them in the issue.

• for use of child documents in a website, I developed code to replace a specific text in a quarto.yml template with titles for a TOC and references to the corresponding .qmd child documents (see code starting here). It seems to work fine except for the fact that the preview is not running well after rendering due to this reported issue. Would it be an idea to add this as a separate function? Please let me know if you want me to contribute in this.

I agree it cwould be nice to have this as a separate function. I’d also like to think about how it would integrate with the other autoqmd functions in terms of naming and documentation. Also if you have a basic example to use in the unit tests, please let me know.

@ElsLommelen I have implemented the use of _quarto.yml.
Important: I have changed the name autoqmd_insert_includes() --> autoqmd_insert_children() and the argument qmd_file to target_file.

The vignette is updated.