Skip to content

Latest commit

 

History

History
74 lines (63 loc) · 3.44 KB

index.md

File metadata and controls

74 lines (63 loc) · 3.44 KB
layout root permalink
lesson
.
index.html

{% include gh_variables.html %}

Use the New Lesson Infrastructure!

Our new lesson infrastructure, The Carpentries Workbench became the default for official Carpentries lessons in May 2023.

The Workbench is designed to be more accessible and easier to use than the styles infrastructure by separating tools from the content. As such, using this repository for lessons is no longer supported by The Carpentries Core Team.

If you would like to create a new lesson, we encourage you to use The Workbench templates below.

Resources

For guidelines on how to develop curriculum content, please visit The Carpentries Curriculum Development Handbook.

This lesson shows how to use [The Carpentries]({{ site.carpentries_site }}) lesson template. The materials below assume familiarity with tools such as GitHub, Markdown, and Jekyll. For more guidance, please visit the Technological introductions section of The Carpentries Curriculum Development Handbook.

For guidelines on how to help improve our lessons and this template, please see [the contribution guidelines][contributing]; for guidelines on how to set up your machine to preview changes locally, please see [the setup instructions]({{ page.root }}{% link setup.md %}).

Prerequisites

Use the .prereq style to specify prerequisites. {: .prereq}

Ten Things You Need To Know

  1. Don't panic.
  2. Create a new lesson by using GitHub Import, not by forking.
  3. Run bin/lesson_initialize.py once in a new lesson repository to set up standard files.
  4. Run make lesson-check to check that the lesson is formatted correctly.
  5. Put lesson episodes in _episodes (or _episodes_rmd if you are writing in RMarkdown).
  6. Run make serve to preview the lesson website locally.
  7. Do not commit the generated HTML files in the _site directory.
  8. Style blocks and code samples by putting {: .stylename} on a newline after the block or code.
  9. Put solutions inside challenges using nested blockquotes.
  10. File issues and template fixes in the [styles repository][styles], and enhancements to this documentation in this one. {: .checklist}

{% include links.md %}