PDF versions

[jmarshrossney]

We need to produce pdfs of these reports, deposit them to NORA, and share these along with the code/data DOIs by 30th June.

Ideally these pdfs would be nicely formatted, but they will likely not be as accessible as the website, so we should make sure that a link to the site is highlighted in them.

I think we will need to have separate pdfs for the reports. We could aggregate into a single one using the book project type by Quarto, and this would allow cross-referencing of e.g. equations between the reports. However, I don't really think of these reports as chapters of a book, hence why I went down the multi-doc/website route here.

[jmarshrossney]

The summary and technical supplement do not compile to pdf without removing certain HTML elements (leaflet maps and outputs of terra::plot I think). I tried placing them inside {.content-visible when-format="pdf"} but to no avail. Same issue with LaTeX and Typst.

Simplest solution is just to "print to pdf", which actually looks ok although none of the links will work.

Otherwise I think we need to make a branch and replace all these HTML plots with PNGs.

This got me thinking about whether we need a PDF output at all, and if so, whether it should be a "first class citizen". Also, whether we need to deposit on NORA or can just use Zenodo.

In reverse order:

• We may be obliged or at least encouraged to deposit PDFs on NORA, since part of the work (SPEAK) was NERC-funded.
• But that does not have the same deadline as BioDT, and there is no reason not to make use of Zenodo to provide a DOI for the HTML version of these reports.
• I see no particular need for PDFs to look amazing. I don't see anyone printing these, and even with a lot of effort the HTML will look better on most devices and be more featureful.
• It's probably good form.