As part of the public history aspect of the course, it’s important to learn how we can we work collaboratively and non-destructively on a public history website like Metahistory. We all have the ability to create, edit, and delete files for the course GitHub repository, but this is a bit dangerous to allow for the entire Metahistory site. Accidents happen. And it’s much less stressful to create or edit essays knowing that you can’t really mess anything up.
So, we use a really neat feature of GitHub to allow everyone to make their own copy of Metahistory 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 work environment. There is a little technical terminology here and there that we need to learn so we can communicate effectively.
In GitHub speak, forking means to create your own copy of someone else’s repository for you to edit privately.
Forkbutton in the upper right corner (don’t click the number).
unm-historiographyin 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). One terminology point here: the actual live repository at
unm-historiographyis the remote repository; the one you have under your own GitHub account is the local repository.
Now that you have a “local” copy of the repository, you can make it create a live site that shows you how the essays look online rather than just as Markdown text as we see in the repository. This is basically a clone of the existing Metahistory website, except it is connected to your own repository.
Settingsnav link near the top of the page
Pagestab (second from the bottom) on the left nav
Noneand change it to
Keep this tab open in your browser, as you’ll need it in the next few steps.
Move on to the next instruction page on editing an existing page, which you will do for your next assignment.