Support Quarto Projects

[storopoli]

Quarto projects have a _quarto.yml and they have nice features:

• A way to render all or some of the files in a directory with a single command (e.g. quarto render myproject).
• A way to share YAML configuration across multiple documents.
• The ability to redirect output artifacts to another directory.
• The ability to freeze rendered output (i.e. don’t re-execute documents unless they have changed).

Reference: https://quarto.org/docs/projects/quarto-projects.html

[MichaelHatherly]

The ability to freeze rendered output (i.e. don’t re-execute documents unless they have changed).

@storopoli any idea what the behaviour here is meant to be if a data source that is used in a notebook changes? Or if a project/manifest used in a notebook changes? Does this freezing only depend on qmd source itself?

[storopoli]

I think that it should track the Project.toml. Data, on the other hand I think is out of the scope of quarto, but I could be wrong.

[MichaelHatherly]

Yeah, that freeze behaviour appears to be pretty basic and does not consider data dependencies outside of the notebook if I'm reading it right. Perhaps that's fine, but also, it's not all that ideal, will result in stale notebooks down the line.

[MichaelHatherly]

A way to render all or some of the files in a directory with a single command
A way to share YAML configuration across multiple documents.

Probably covered by @jkrumbiegel's work on quarto, right? Or do you reckon we need anything else done here for that?

[jkrumbiegel]

As we ingest the project options sent by quarto in QuartoNotebookRunner now, parent project settings affect renders of qmd files as expected.

Freezing, I'm not sure about. I think that might need more specialized implementation in quarto.

[MichaelHatherly]

Closing since this is dealt with by upstream quarto itself.