-
Notifications
You must be signed in to change notification settings - Fork 26
Closed
Description
The dynamic metadata documentation is very well written and the first example of use and its output it's very helpful.
I have minor suggestions:
- R chunks in the example do not properly show the #| options. This is probably simply a formatting thing because there's an explicit mention to it, e.g.:
Note the #| output: asis chunk option - this is essential:) - The examples chosen do not show the full range of possibilities that this new functionality offers. Even updating the parameters outside of the document via
quarto render test.qmd -P ...benefits from this new functionality (thanks to the sequential order in which code is executed). There are two veiled references to this:This functionality addresses a key limitation where Quarto metadata must traditionally be static and defined in the document headerandAnd so, it wll make the metadata available for use throughout the document., but I think the documentation would benefit from a more explicit mention. - While the email variants example demonstrates the new functionality, readers unfamiliar with Posit Connect or the Quarto Email Extension might benefit from brief contextual links to related documentation.
I would say that had I read this documentation earlier, when I learnt about the existence of quarto::write_yaml_metadata_block, I wouldn't have required assistance applying this to my use case.
cderv
Metadata
Metadata
Assignees
Labels
No labels