Thank you for contributing to the material! This document provides an introduction to the ways the lessons are organized, the tools we use to render them, and the type of modifications we expect.
The lessons are generated from markdown documents. These guidelines will walk you through the repository organization, the markdown basics, and any additional information.
Every lesson is a single folder within the lessons
directory. Each lesson
folder is called XX_keyword
, where XX
is the lesson number, and keyword
is
a brief description of the lesson. The slides themselves are in a file called
index.md
. Do not use another filename. For example, the demonstration
lesson markdown file can be viewed here. This
demonstration lesson showcases most of the features you can use in your slides.
You are free to add other directories to your lesson. Images go in images
, and
PDF files in pdf
. For example, a lesson repository could look like:
01_management/
index.md
images/
image1.png
image3.jpg
pdf/
one-pager.pdf
The markdown documents are rendered into a website using Jekyll. The slides
themselves are rendered using remarkjs. The rendering is done using github
pages, which builds the site from the master
branch. You can build the site
locally with jekyll serve -w
, and it will be available at
http://localhost:4000
for you to review.
The stylesheets are defined in resources/styles
, and rendered to
resources/dataone.css
using lessc
(just type make
from the root).
- Create a fork of the repository into your github account
- Modify the files that you want to change
- Submit a pull-request against the
master
branch of this repository - Your changes will be reviewed
- Open an Issue on this repository.
Check that the title
field of the YAML header (the first line of each
lesson) is in quotes.