Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rubric or user-specified chunk types #1

Open
daviddalpiaz opened this issue Nov 21, 2017 · 4 comments
Open

Rubric or user-specified chunk types #1

daviddalpiaz opened this issue Nov 21, 2017 · 4 comments

Comments

@daviddalpiaz
Copy link
Contributor

  • rubric = TRUE to add comments that only appear in a *-rubric.pdf document.
  • xyz = TRUE to add a user specified chunk and file type?
@coatless
Copy link
Collaborator

My thought on the next iteration is to define a custom markdown engine in a similar manner to how bookdown generates theorem, definition, lemma, et cetera environments. May be a bit more robust than the current approach.

We could still add a flag for "xyz" tagging. Likely need to figure out the best way to specify how the flag should propagate to the two output results. Maybe create a document object with the intended overflags for each one?

@daviddalpiaz
Copy link
Contributor Author

The former is probably the way we should go. You raise a good point about tag propagation. Currently students are exposed to solution = TRUE.

@coatless
Copy link
Collaborator

So, I've toyed around with this. The issue we'll run into with going from:

```{asis, solution = TRUE}

```

to:

```{solution}

```

is this assumes only text is being displayed. Having the solution = TRUE flag allows us to still use the r engine, e.g.

```{r, solution = TRUE}

```

How would you feel if I just removed the tagging architecture on the rendered Rmd files? (e.g. delete solution = TRUE, et cetera.)

@daviddalpiaz
Copy link
Contributor Author

Just removing the tagging in the output is what I had in mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants