Skip to main content

Digital History, Digital Archaeology, Simulations, Games, AR, Romans. Method & Theory.

Guiding the MA in Digital Humanities 2015/2016 Programme at Carleton University

electricarchaeology.ca

twitter.com/electricarchaeology

carleton.ca/dighum

 

Building your own website with your github repository

2 min read

Now you've learned how github works, here's a neat way of getting a personal website/journal/open notebook up and running. 

1. Fork this repository https://github.com/barryclark/jekyll-now

2. Rename your copy of the repository in the settings, by hitting the cogwheel icon, and changing the repo name from 'jeckyll-noww' to  (with no )

3. Click 'rename'.  Scroll down - see the green bar that says 'your site is published at shawngraham.github.io!' (yours'll be different, of course). Click on that link - your site is live!

4. If it isn't, we'll just give Github a nudge. On the main page for your repo, click on the file called _config.yml 

5. Click the pencil icon, so you can edit it. Change line 6, to put in your name. Go to the bottom of the page and hit the green commit changes button. Open a new browser window, put the URL in: and ta da!

A more detailed set of instructions is at http://www.smashingmagazine.com/2014/08/build-blog-jekyll-github-pages/

-----

You can add new posts to your new blog by cloning the repo on your desktop, and then saving .md files into the  _posts folder. Note that the naming convention has to be the same as the example post. Then sync with your repo, and your changes are published to the web! 

There are lots of reasons why you might do this, but two very good ones is a) free b) you keep control because your materials are on your own machine c) it's fast - the site is static and so no time is wasted computing what the page ought to look like d) it's secure. Well, more secure than many options (ask me about the Heritage Crowd project sometime).

 

What is community building?

1 min read

I expect you to comment on each other's work, constructively. You do that through status updates, posts, audio, etc, here on this site. When someone adds a new tool tutorial to our github repo, I want you to try it out. When someone has uploaded or completed an assignment, take a look. If someone has made a really powerful seminar presentation, I want to see reflections. If there was something in the readings that you feel didn't come out in the discussion, carry on the discussion here. Reach out to the wider DH community - tweet links to our stuff; bring links back here for us to look at. 

This site is our public facing hub. When I assess 'community building', I'm looking at how you made this online space a place worth being at.

Tag your posts accordingly - , , ... there is no hard rule about how you tag, just make sure it's descriptive, but in general, if there's something you want me to take into account at the evaluation stage, use