This repository was archived by the owner on Nov 1, 2017. It is now read-only.
Classnotes Templates for Easier Post-Event Material Generation#149
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


The current process for generating event/training classnotes is tedious. It also includes copy-pasting of resources. This workflow needs to 💀.
This undertaking separates the teacher information (name, GitHub link, Twitter handle), resources, and CLI to maintain a DRY approach to the content and allow simpler maintainence of resources across all post-event classnote documents.
The new classnotes markdown will now focus on the page's content by means of the YAML, and the content body being the only custom field for CLI.