Provide outline for skills level and objectives

[avahoffman]

Adding a scaffold for users of this template to add skills / objectives. Mirrors what's in https://github.com/jhudsl/GDSCN_Book_SARS_Galaxy_on_AnVIL/blob/main/index.Rmd

[github-actions[bot]]

No spelling errors! :tada: Comment updated at 2022-09-20 with changes from 7e4031acf0db18edb3c7247b7f1081c9b3b343df

[github-actions[bot]]

No broken URLs detected! :tada: Comment updated at 2022-09-20 with changes from 7e4031acf0db18edb3c7247b7f1081c9b3b343df

[github-actions[bot]]

Re-rendered previews from the latest commit:

• See preview of Bookdown here
• See preview of Coursera/Leanpub version here
• Download the preview of .docx file

Updated at 2022-09-20 with changes from 7e4031acf0db18edb3c7247b7f1081c9b3b343df

[KatherineCox]

1. I think that's a great idea, thanks for adding this!

2. I'm not sure it needs to be commented out?

Or perhaps only comment out the things that might be untrue:

• Novice: no genetics knowledge needed
• Novice: no programming experience needed
• Learning objectives for this activity come from the Genetics Core Competencies:

I can see the argument for commenting out the whole thing, so an un-filled-out box doesn't show up in the rendered book. But as an author I'd be more likely to notice and remember to add them here if I had the box staring me in the face when I opened my book, haha. I'm okay with either though.

3. Looks like there's some related discussion in https://github.com/jhudsl/AnVIL_Book_WDL/pull/16

Mainly discussing if/how to include a statement that you need access to a Terra Billing Project Copying it here to have the conversation going in one place:

Agree on trying to be consistent! Happy to move Learning Objectives to the third position, but I'd like to avoid having two {.notice} if possible. Two questions:

Do you think it's worth stating that it requires access to a Terra Billing Project on all the hands-on books? Or is that just a given?

Thoughts on the friendlier title Skills Level vs more general Prerequisites (which would allow for things like Funding)?

Thoughts on these:

• I likewise don't have a strong preference for whether Learning Objectives comes before or after the prereqs
• I agree having multiple boxes starts to feel cluttered, so a more generic "Prerequisites" might be useful as the title.
• I think I'd lean towards leaving out the requirement access to a Billing Project; I think that's fairly safe to treat as a given on the front page. We can mention and link out to instructions later, in something like a "Before You Start". But I think the front page should be skimmable, only the important information so the reader can decide whether they want to look further into the book, and from that standpoint, mentioning Billing Projects is extra noise.

4. Duplicate in style-sets/GDSCN/index.Rmd

If we've got something we're happy with, copy if into the GDSCN style-set as well (assuming we want the same thing there, which seems reasonable to me)

[avahoffman]

@KatherineCox great points all around, thanks for taking a look! Will make those changes.

[KatherineCox]

@avahoffman looks good!

• I might add a colon after "Genetics" and "Programming skills", but I think that's a personal preference. I'm fine either way.
• copy NIBLSE to GDSCN index.Rmd

[avahoffman]

GAH thanks for catching that @KatherineCox !