This lesson shows how to use the Software Carpentry and Data Carpentry lesson template. For guidelines on how to help improve our lessons and this template, please see the contribution guidelines; for guidelines on how to set up your machine to preview changes locally, please see the setup instructions.
Prerequisites
Use the
.prereq
style to specify prerequisites.
Ten Things You Need To Know
- Don’t panic.
- Create a new lesson by using GitHub Import, not by forking.
- Run
bin/lesson_inititialize.py
once in a new lesson repository to set up standard files.- Run
make lesson-check
to check that the lesson is formatted correctly.- Put lesson episodes in
_episodes
(or_episodes_rmd
if you are writing in RMarkdown).- Run
make serve
to preview the lesson website locally.- Do not commit the generated HTML files in the
_site
directory.- Style blocks and code samples by putting
{: .stylename}
after the block or code.- Put solutions inside challenges using nested blockquotes.
- File issues and template fixes in the styles repository, and enhancements to this documentation in this one.
00:00 | Lesson Design | How do we design lessons? |
00:10 | GitHub, Markdown, and Jekyll | How are pages published? |
00:20 | Lesson Organization | How are the files in a lesson organized? |
00:30 | Formatting | How are Software and Data Carpentry lessons formatted? |
00:40 | Checking and Previewing |
How can lesson formatting be checked?
How can lessons be previewed? |
00:45 | Using RMarkdown | How to write a lesson using RMarkdown? |
00:57 | Maintenance | What do lesson maintainers do? |
01:02 | Coffee Break | Break |
01:17 | Finish |
The actual schedule may vary slightly depending on the topics and exercises chosen by the instructor.