@@ -98,22 +98,24 @@ is the a URL-encoded form of the latex commands to generate the equation. Here a
9898
9999## Adding a Hands On Example
100100
101+ 1 . Be sure to start from the [ lesson template] ( lessons/lesson_template/lesson.md )
1011021 . Add a new directory to ` ./lessons/<new-example-name> `
1021031 . Add a new line to ` ./lessons/lessons.md ` for the new example
103- 1 . Copy ` ./lessons/lesson_template/lesson.md ` to ` ./lessons/<new-example-name> ` .
104+ 1 . Copy the [ lesson template ] ( lessons/lesson_template/lesson.md ) , ` ./lessons/lesson_template/lesson.md ` to ` ./lessons/<new-example-name> ` .
1041051 . Edit/revise the copied ` lesson.md ` file to create the new lesson
1051061 . You can link to images, source code files that you place in ` ./lessons/<new-example-name> `
106107 using standard Markdown links.
107108
108- I think it would be best put all content related to each hands-on example we develop here
109+ I think it would be best put all content related to each hands-on lesson we develop here
109110into its own separate directory. That means all images, example codes, markdown pages, etc.
110111Then, we can have a separate page (or page hierarchy) that indexes the examples.
111112
112113I know Jekyll has a built-in concept of a ` posts ` object. That is because Jekyll is designed
113114around the notion of supporting blogging. It may make sense to handle each hands-on kinda
114115sorta like a ` post ` in Jekyll. But, I think that also means that content related to each
115116lesson gets scattered across multiple directories (at least given the ** default** ) way that
116- Jekyll seems to handle ` posts ` .
117+ Jekyll seems to handle ` posts ` . We need to investigate proper use of Jekyll further ** after**
118+ we've completed ATPESC.
117119
118120## GitHub Style Primer
119121
0 commit comments