Reformat pkgdown workflow

[VisruthSK]

• Adopted new theme closer to main Stan webpage
• GitHub Action builds and deploys site on releases
• GHA also deploys latest version of site on pushes to master at mc-stan.org/loo/dev/*

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.76%. Comparing base (b4c12c3) to head (89bdf92).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #292   +/-   ##
=======================================
  Coverage   92.76%   92.76%           
=======================================
  Files          31       31           
  Lines        2986     2986           
=======================================
  Hits         2770     2770           
  Misses        216      216           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[VisruthSK]

On second though, if possible, it might make more sense to automatically build and deploy sites to https://dev.mc-stan.org/loo/ and setup another workflow to generate the site on releases which would get pushed to https://mc-stan.org/loo/.

[VisruthSK]

on:
pull_request:
should be removed once the workflow is confirmed to work.

Obviated

[jgabry]

On second though, if possible, it might make more sense to automatically build and deploy sites to https://dev.mc-stan.org/loo/ and setup another workflow to generate the site on releases which would get pushed to https://mc-stan.org/loo/.

Yeah I agree that it would be preferable to only publish the site on https://mc-stan.org/loo/ when we do a release. If we publish at the main URL on every commit to master then the website could advertise unreleased features that aren't available on CRAN yet.

[jgabry]

I think this looks good. But the regenerated website pages that are part of this PR are for the development version of loo, not the released version. So if I merge this won't it update the website to the development version?

[VisruthSK]

Right, I'll move files from the gh-pages branch into the docs folder then

[VisruthSK]

https://github.com/stan-dev/loo/actions/runs/15627201098/job/44023603976

Looks like the vignettes get built too.

[VisruthSK]

Updated _pkgdown.yml to link to Aki's CV page. Closes #294

[VisruthSK]

Closes #208.

[VisruthSK]

@jgabry this should build the site in the pages directory and doesn't add any website files to the main branch. I'm running the pkgdown action again but hopefully it passes and this can be merged.

[jgabry]

How would you feel about moving the pkgdownConfig repository into the stan-dev organization (with you as its maintainer if you want)?

[VisruthSK]

Sounds good! I had vaguely planned for this anyway. I'll transfer ownership and fix the config later today.

[jgabry]

Sounds good. Let me know if you run into any issues transferring it.

[VisruthSK]

I don't have permission to transfer the repository it seems--probably because I can't make repos under the org?

[jgabry]

Cool thanks, I think this looks great. I put two questions in review comments

[jgabry]

I think this is ready to go except for updating the config after transferring the repo.