Chromium is used for some of the additional features like graphviz/mermaid diagrams IIRC, it is not used for the core functionality[1]. I also see crashes when using my template, though this doesn’t impact the compile (mermaid figures are made, then chromium crashes only as it shuts down; it is a macOS bug with the older version of chromium quarto installs, doesn’t happen in Linux at least).
Don’t compile the sections that use graphviz/mermaid and see if the crash goes (it should).
I wouldn’t worry about it as I doubt you’ll be using mermaid? If you install Chromium yourself (using homebrew etc.) I tink Quarto uses that version and you don’t need the quarto tools
version).
My original template (on which ScrivQ is based) uses a single metadata file, though this template doesn’t have the document splitting mod Bernardo made. I imagine you can modify Bernardo’s front matter design to use a simple metadata file, though he does quite a few things with his front-matter and may need some input from him. It should be fairly straight forward to also modify my templete to use his script for document splitting if that is what you need.
I think the binder-as-metadata concept ScrivQ uses is very clever and cool conceptally, but it adds a lot of complexity to the compile settings (each YAML level uses a different section etc., lots of settings I never use are still present in the UI) and I personally prefer to use a YAML file.
[1] the technology is cool: mermaid is a regular app, and they have compiled it using webassembly, treats the browser as a virtual machine, therefore you don’t need to precompile binaries for different operating systems etc.