add blog and images

[DCEW]

The Quarto workflows started failing after switching away from the Quarto render action: CI had R available, but not the knitr / rmarkdown packages required to render posts with frozen R content. This change restores the repo’s intended non-executing CI render path and installs only the R packages Quarto needs to parse those documents.

• Workflow behavior

  • Keep both preview and publish workflows on quarto render . --execute false
  • Remove the split between trusted and fork PR render paths so CI follows one render mode consistently

• R runtime dependencies

  • Add r-lib/actions/setup-r-dependencies@v2 to install the minimal packages Quarto needs:
    • any::knitr
    • any::rmarkdown

• Contributor guidance

  • Update the README note on CI behavior to reflect that Actions now provides a minimal R setup for rendering, while computation still needs to happen locally and be committed via _freeze

Example workflow change:

- name: Setup R dependencies
  uses: r-lib/actions/setup-r-dependencies@v2
  with:
    extra-packages: |
      any::knitr
      any::rmarkdown

- name: Render
  run: quarto render . --execute false

[github-actions]

PR Preview Action v1.4.8
🚀 Deployed preview to https://The-Strategy-Unit.github.io/data_science/pr-preview/pr-455/
on branch gh-pages at 2026-06-22 17:11 UTC

[tomjemmett]

Didn't I create a PR a while back to purposely remove the need for R and its dependencies? Or was that a different repo...

[ai-mindset]

Didn't I create a PR a while back to purposely remove the need for R and its dependencies? Or was that a different repo...

You probably did. I was experimenting with GitHub Copilot but I'm not happy with the outcome. Will revert back to cd5cf14.

Edit: @tomjemmett how do pages get rendered without R?

[tomjemmett]

any computations should be committed to the _freeze directory (render local). otherwise, you should not need to render.

there are some caveats, see the readme. some things like code-folding seem to require rmarkdown and knitr to be available for no good reason, so it's best to avoid those features

[ai-mindset]

any computations should be committed to the _freeze directory (render local). otherwise, you should not need to render.

there are some caveats, see the readme. some things like code-folding seem to require rmarkdown and knitr to be available for no good reason, so it's best to avoid those features

The cuplrit most likely was a forgotten

```{r lockfile}
...
renv::use(lockfile = "renv.lock")
```

I hadn't deleted when I updated our Using Git and GitHub page. code-fold: true wasn't relevant here.

[DCEW]

Not sure what to do with this one now TBH given the confusion - will let @tomjemmett approve this PR

[tomjemmett]

@DCEW not read any of the content, so not really in a position to approve/disprove, but it doesn't seem to be borking the deployment anymore