- Nov 27, 2014
-
-
Aaron O'Leary authored
This means that you can trigger div creation by 1. Using a special title 2. Using a special class on an arbitrary title
-
- Nov 26, 2014
-
-
Raniere Silva authored
- Use UPPERCASE for global constants - Add Learning Objectives to SPECIAL_TITLES - Fix samples
-
Aaron O'Leary authored
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>
-
- Nov 25, 2014
-
-
Rémi Emonet authored
-
Rémi Emonet authored
-
- Nov 17, 2014
-
-
Greg Wilson authored
-
- Nov 16, 2014
-
-
Raniere Silva authored
and others small fixes.
-
- Nov 15, 2014
-
-
Greg Wilson authored
-
- Nov 14, 2014
-
-
Raniere Silva authored
-
- Nov 12, 2014
-
-
Aaron O'Leary authored
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').
-
- Nov 09, 2014
-
-
Greg Wilson authored
-
Greg Wilson authored
* 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).
-
- Oct 23, 2014
-
-
Greg Wilson authored
-
- Oct 21, 2014
-
-
Trevor Bekolay authored
-
Trevor Bekolay authored
-
Trevor Bekolay authored
This is up for discussion, but at the moment is the minimal set of files needed to be a Software Carpentry lesson.
-