https://github.com/coderefinery/example-lesson
Empty example lesson.
https://github.com/coderefinery/example-lesson
Last synced: 5 months ago
JSON representation
Empty example lesson.
- Host: GitHub
- URL: https://github.com/coderefinery/example-lesson
- Owner: coderefinery
- License: cc-by-4.0
- Created: 2016-11-21T20:02:19.000Z (over 9 years ago)
- Default Branch: gh-pages
- Last Pushed: 2019-10-31T11:07:36.000Z (over 6 years ago)
- Last Synced: 2025-09-10T04:47:52.313Z (9 months ago)
- Homepage: https://coderefinery.github.io/example-lesson/
- Size: 152 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Example lesson
## Credit and license
- https://coderefinery.github.io/example-lesson/license/
## How to include jekyll-common
```shell
$ git submodule add https://github.com/coderefinery/jekyll-common.git jekyll-common
```
## Tips
- Get inspired by Software Carpentry, e.g.: https://biologyguy.github.io/python-novice-gapminder/
- Students interacting is better than students only listening
- Share your sources and exercises early to get early feedback
- Do not be afraid to share unfinished and badly structured work
- Make it available and restructure later, do not gold-plate too early
- Use ideally Markdown or RST or Jupyter notebooks (easy to generate nice pages from these formats)
- Divide your session into modules and files
- Try to make it interactive: mix type-along sessions with short exercises
- Motivate each session
- Set and document goals for each module
- Mind the cognitive load (better few messages that are clear rather than too much information)
- Involve others to get your material tested
- Create a new repository for each session, makes it easier to move things around
## Contribution
Yes please! Please extend, edit, correct, suggest, and discuss.