Github Pages Markdown Map

Markdown is a conversion process that takes simple text docuemnts and configuration files and turns them into a full static website directory. Github Pages can automatically generate a simple website based on Jekyll’s markdown language. Let’s look at a simple mapping of the default directories used by Jekyll, to get an idea of how markdown can make for an easy-to-update website.

This guide is based off the Jekyll Step by Step Tutorial, and is very helpful when getting started with markdown.

The basic file structure:

+-- assets           (Site code and images that are imported to pages for formatting)
|   +-- css
|   +-- images
|   +-- js
+-- _authors         (Bio's about each contributing author)
+-- _data            (Navigation markdown file)
+-- _includes        (html pages to include in other pages, like the navigation bar)
+-- _layouts         (html layouts for types of pages)
+-- _posts           (blog post markdown files)
+-- _sass            (main css style, as scss)
+-- _site            (where the command-line ruby tool generates the site)

Let’s explore each folder a little bit more: «««< HEAD * assets If you have javascript or images, they can go in the appropriate files. The CSS files are actually generated by the Jekyll conversion, from the SCSS files (see the _sass section). =======

assets

If you have javascript or images, they can go in the appropriate files. The CSS files are actually generated by the Jekyll conversion, from the SCSS files (see the _sass section).

b4a8bc18a2f1e5692a6c1f5f3c611e91bbdb865e

_authors

This folder contains

_data

_includes

_layouts

_posts

_sass

_site