Support better way for forked repositories to update core theme patches

[staeiou]

There is one logistical issue with a ready-to-fork template theme like academic pages that makes it a little tricky to get bug fixes and updates to the core theme. If you fork this repository, customize it, then pull again, you'll probably get merge conflicts. If you want to save your various .yml configuration files and markdown files, you can delete the repository and fork it again. Or you can manually patch.

I'm not sure what the best way is to support this, so for now, I'm curating a manually-curated list of bugs that have been fixed since this project was released, currently in README.md. If you have a bug, you can go through and manually update. But if you have a better idea about how to support this, please let me know!

[staeiou]

I'm now managing this through issues, which will be tagged with 'code change' and should have a comment in the issue linking to the commit or diff comparison, so patching is easier. Updated README.md and CONTRIBUTING.md to reflect this.

[rjzupkoii]

A user asked about this is the discussions (see #1938), so that should also be updated when this is addressed. One idea is that since most of the files that are typically edited are already known, it may be possible to write GitHub Action (ex., Fork Sync) specific to Academic Pages that backs up the relevant files that would be clobbered before restoring them.