Digitizing Medieval Archives
  • Introduction
  • Overview of the Course
  • Assignments
  • Lead a seminar
  • Readings
  • Week 1 & 2 - Setting Up
    • Signing Up
    • Using Twitter
    • Twitter Strategies
    • Twitter Abbreviations
  • Week 3 - Omeka
    • Dublin Core
  • Week 4 - Github
    • Markdown
    • Github
    • Turning Github into a website
    • Markdown II (Optional)
  • Week 5 - Writing Supports
    • Your first transcription
    • Getting prepared for Transkribus
  • Week 6 - Palæography
    • Distinguishing Late Medieval Scripts
    • Handwriting Analysis Tools
    • Installing Medieval Unicode
    • IRL Abbreviations
  • Week 7 - Abbreviations
    • Transcribing with Transkribus
    • Transcribing
    • Java 8
  • Week 8 - Codicology
    • Codicological Spreadsheet
  • Week 9 - Liturgical Genres
    • Medieval Liturgy - Basic Bibliography
  • Week 10 - Cataloguing
    • Template for Folio Cataloguing
  • Week 11 - Workday
  • Week 12 - Whetting your Digital Appetite
  • Week 13 - The Theory of the Digital
    • Github Project Boards
  • Week 14 - The Promise of DH
    • Criteria for Evaluating DH Projects
  • Week 15 - Capturing Manuscripts
    • How to take photos of documents
    • Image File Formats
  • Week 16 - IIIF
    • Our IIIF Images
    • Understanding IIIF Image Presentation
    • Using IIIF Manifests
  • Week 17 - IIIF Annotations
    • Annotations in Mirador
    • Annotations with Transkribus
  • Week 18 - Online Exhibits
  • Week 19 - TEI
    • Look at a TEI folio description
    • Digital Latin Library
    • TEI export from Transkribus
  • Week 20 - Accessibility and Longevity
  • Week 21 - Work
  • Week 22 - Work
  • Week 23 - Presentations I
  • Week 24 - Presentations II
  • Week 25 - End of the Line
  • About
Powered by GitBook
On this page
  1. Week 4 - Github

Markdown

PreviousWeek 4 - GithubNextGithub

Last updated 6 years ago

Markdown Classwork

The benefit of using Atom as your Markdown editor is that it comes with pre-installed plugins for Markdown: ‣ Language-Markdown (which highlights syntax), ‣ and Markdown-preview (which allows you to view a real-time preview of your Markdown product).

Step 1: Open Atom and locate your repository on your hard drive (which you created this in week 2 and called it something like "[username]/HIST4006"). In this repository there should be two folders: one entitled "Classwork" and the other "Folios." Open the HIST4006 repository, then the Classwork folder (which should be visible in the sidebar). In this folder, you will find a file called Sample.Kate.profile.md. Open it and you will see a file that looks like this:

# This is Kate's Markdown file
***
Here is a list of reasons I joined HIST 4006A:

- improve my __digital humanities skills__
- learn _more_ about codicology and palaography
- make an **online project** I can put on my CV
- meet *awesome* medievalists

### More about me
Here is a link to [my Hcommons profile](https://hcommons.org/members/katebrasseur/)

Here are four emoticons that represent me:

1. :european_castle:
2. :cat2:
3. :cherry_blossom:
4. :rainbow:

Step 2: In Atom, click File >> Save As... and save the renamed file in the Classwork folder using the following naming convention:

Your last name.your first name.profile.md

Step 3: Navigate to the Packages tab and select Markdown Preview >> Toggle Preview to see a live preview of your Markdown in action. In a new column, you should see the code translated to the visual appearance of the Markdown file.

Step 4: Replace the example text with your own, check to make sure you get the syntax correct by checking the Markdown Preview. Once you are satisfied with your work, learn how to contribute the file to our repository on Github in the .

next lesson
Markdown with Atom