This is needed to enable users jump to glossary entries.

Add validation methods and refactor ast helpers to separate class

Add tiny logging message; prep for first push to github fork

Start adding tests

Fix errors revealed by unit tests

Update validator to check heading order; tests passing

Validation of links and changes to heading validation

Tiny comment cleanup; push to share version with swc

Add some descriptive comments and create minimal validator example (for instructors.md) to demonstrate subclassing

Split helpers to separate file and update for newest index.md template

Grooming

Bring up to spec with newest versions of lesson templates. Add tests to ensure all templates pass validation.

Saner default assumption about markdown file locations

Add skeletons for remaining validators. Incorporate ranier's code for batch validation.

Code changes for single-file python 2 and 3 compatibility.

Refactor out template validation logic in prep for cmd line rework

Proof of concept refactor to command line sig for @rgaia-cs (issue #34)

With no path provided, default to curdir, not a hard-coded default

Implement license and discussion validators. Some test cleanup.

Validate file links against page titles. Add line length check.

Fix python3 hash error

Rename validator to check

Conflicts:
	tools/validate_markdown_template.py

Enforce section heading levels + pep8 cleanup

Improved link validation for non-html files

Validate images as well as links

Verify that all headings are exactly level 2

Link text validation based on document header "subtitle" instead of "title".

Adjustments based on run against the SQL repo.

Fix links to topics

By default only show erros and warnings to user

- Add another argument for CLI to enable debug log level
- Change some log message to debug instead of info
- Add file information for errors and warnings

Fix import at check

From [PEP8](https://www.python.org/dev/peps/pep-0008/#imports)

> Imports should usually be on separate lines, e.g.:
>
> Yes: import os
>      import sys
>
> No:  import sys, os

Heading bugfixes, update failing tests, and cleanup. fix swcarpentry/lesson-template#39, swcarpentry/lesson-template#42 .

Add validation of glossary

Slight clarification to log messages.

Skip validate some links in index

Fix super() call for python2; avoid mutable default argument.

Lesson template validator.

This means that you can trigger div creation by

1. Using a special title
2. Using a special class on an arbitrary title

- Use UPPERCASE for global constants
- Add Learning Objectives to SPECIAL_TITLES
- Fix samples

Previously, Div creation was triggered by a Blockquote that began with a
header that contained a single class that was in a list of special
classes.

Now, Div creation is *also* triggered by a Blockquote that begins with a
header that has it's text contained in a list of special titles. The
title is used to lookup an appropriate class to give the Div.

In particular, 'prerequesites' is a special title, giving the class
'prereq'.

This input:

    > ## Prerequesites
    >
    > A short paragraph describing what learners need to know before
    > tackling this lesson.

will trigger this output:

    <div id="prerequisites" class="prereq">
    <h2>Prerequisites</h2>
    <p>A short paragraph describing what learners need to know before
    tackling this lesson.</p>
    </div>

and others small fixes.

This filter converts all blockquote-with-attributes to
div-with-attributes.

A blockquote-with-attributes is defined as a blockquote that has a
header with attributes defined on it as it's first element, e.g.

    > # valid blockquote {.class}
    > text

This example would be converted into this markdown:

    <div class='class' id=id>
    # valid blockquote
    text
    </div>

And the equivalent html.

The class must be one of the allowed classes defined in the filter (i.e.
one of 'callout', 'objectives' or 'challenge').

* Add `.nojekyll` to stop GitHub trying to compile.
* Get rid of Jekyll `_config.yml`.
* Create placeholder `css` and `img` directories.
* Create `pages` directory with source for web pages.
* Move all Markdown files into `pages`.
* Move `tools` into `pages` (because that's where people will mostly work).
* Move `_includes` and `_layouts` into `pages` (because that's where we'll compile).

This is up for discussion, but at the moment is the
minimal set of files needed to be a Software Carpentry lesson.