Publish action too slow

[camwest5]

It's taking 6-12min to run the website publish action. Can we speed this up? We shouldn't need to take so long (i.e. re-render) for minor markdown changes.

[stragu]

Using the binaries from the Posit Package Manager might help, see e.g. https://rstats.me/@adamhsparks/116361189722611684. Although it sounds like it would only be useful if we used pak instead of renv? And don't we already use a cache in renv anyway?

It seems that the two most costly steps are currently:

1. apt update && apt upgrade
2. rendering of pages

For the first one, I'm wondering about the feasibility of having our own hardware, a small machine that has all the software and only updates / reinstalls dependencies when we want it to.

For the rendering of pages, our quarto freeze settings should mean pages are only rendered when the contents change. Looks like the injection of the "upcoming workshop" banner means that all pages that have a published event are re-rendered entirely. Wondering if using some kind of embed code that's always there could be a solution, e.g. embedding client-side the banner if a separate banner.qmd exists, using includes.