create a code handout of challenges without solutions

Open
#74 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
documentation

Research direction

Start with the sandpaper::build_handout() reference and compare the Download Lesson Handout behavior in the linked R for Ecologists lesson. Then inspect this repository’s lesson structure to identify where the handout is generated. Done means a downloadable code handout contains the challenges without their solutions.

Written by the indexing model from the issue text.

Description

enhancement

I just found that this action can be done with the sandpaper::build_handout() function.

This probably can generate the button that is at the end of the list of episodes: "Download Lesson Handout". Please, take a look at the following lesson on R for Ecologist

ref: https://carpentries.github.io/sandpaper/reference/build_handout.html

Dominant language
R
Stars
3
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from epiverse-trace/tutorials

All issues in epiverse-trace/tutorials

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.