Finalise quarto migration

[SamHames]

Checklist and issues I'm investigating:

• why is the repository so big? The checked in cache seems quite big, need to investigate whether that's necessary or can be trimmed down.
  • Add gitignore for caching
• Redirects from old URLs to new URLs
• Github pages setup
  • output to docs folder to use default gh-pages config
• Documentation/Readme
  • How to build site as a whole + individual pages
  • Setting up a new tutorial
  • Updating site navigation
• Create an renv for specifying dependencies for reproducible builds
• Work out procedure to archive the existing repository and then seamlessly replace
• Google analytics
• Confirm everything is migrated across

[SamHames]

Okay, so it turns out this isn't going to work, everything is going to break if we deploy it. There's a whole lot of maintenance work to do because this kind of thing is all over the place. Since this means that everything currently depends on the current site, this isn't going to happen until next year, and we're going to need to work out a more incremental migration pathway, sorry @laurenceanthony

[laurenceanthony]

Hi,
Are you looking at my repo?
I thought I addressed all of these cases and simply copied the data into the correct location. Even if I didn't, it should be relatively easy to locate all the references, correct the path to the local one, and then copy over the data. How many cases are we actually talking about?

[SamHames]

Yes, the pattern is everywhere - string search for slcladal.github.io. And yes, it's of course fixable, but I have one working day left this year and I don't want you to put any more work into this.

[laurenceanthony]

OK. So, there are 712 cases. They are all of a very similar variety. I'll look into this. It should be a simple search and replace operations. Can you figure out the other remaining issues (e.g. redirects)?