-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add a rendering step that uses different _bookdown.yml
file(s)
#176
Comments
@KatherineCox not hard. I can play around with something! |
@KatherineCox I've created a way to render a student guide from separate bookdown and output ymls over at #177 . For now, Leanpub will use the original bookdown set. If the student materials need to end up on Leanpub, I wonder if it warrants its own repo at that point. |
Awesome! re: Leanpub - I haven't dug into the details of either the GitHub actions or Leanpub myself, so I'm happy to follow your recommendations there. If it's too complicated to make that happen in a single repo, it's not that hard to make another repo and either sync or borrow_chapter to keep them up-to-date with each other. |
@avahoffman how hard would this be?
A lot of our GDSCN books are aimed at instructors. It would be nice if we could use a different
_bookdown.yml
file to render the student-facing content in a stand-alone output. Two things I could imagine doing with this:I looked into this a little bit on the bookdown side, and I didn't see a way to manage this with a single call to
bookdown::render_book()
(i.e. by changing settings in _output.yml or something) so...render_book()
for each variant of_bookdown.yml
@cansavvy is this something that would be useful for OTTR? I filed the issue here in
AnVIL_Template
since my use case is fairly specific to our GDSCN books, where we're writing a book aimed at instructors which contains chapters for them to give their students. But perhaps there are other more general use cases?The text was updated successfully, but these errors were encountered: