As part of the public history aspect of the course, it’s important to learn how we can we work collaboratively and non-destructively. And it’s much less stressful to create or edit essays knowing that you can’t really mess anything up.
So, we use a feature of GitHub to allow everyone to make their own copy of Campus History and edit that without fear of breaking anything. When a set of changes are done and you want to publish those changes on the live site, you can easily do that. This guide describes the process of setting up your own copy of Campus History.
In GitHub speak, forking means to create your own copy of someone else’s public repository so that you can play around with your own copy and leave the original alone.
Fork
button in the upper right corner (don’t click the number).unm-digital-history
in the URL, and the URL for your “fork” of it will have your GitHub username. Either way, the list of files looks exactly the same (for now).You now have a “local” copy of the repository, which is all files that make the website work. Now, let’s enable your own working copy of the Campus History site. As you edit your essay, you can see how the essays actually look online (instead of just Markdown files with code snippets).
Settings
nav link near the top of the pagePages
link on the left navNone
and change it to master
Save
buttonActions
tab, and wait for the orange yellow dot to turn greenSettings
and then Pages
again.