search

FredHutch / wiki

SciWiki: Collective KnowledgeBase for Scientific Data and Use
https://sciwiki.fredhutch.org
Other
36 stars 46 forks source link

Come up with some sort of decision tree flow to the wiki homepage #403

Closed Chilliwack closed 4 years ago

Chilliwack commented 5 years ago

What is the starting choices? Next? Next? How deep does the flow go? Can we get it also linked to the side so a user can get back to it if lost?

vortexing commented 4 years ago

Perhaps this could be a separate project - a decision tree that links to different parts of the Wiki. OR, if you engage PI's here, you could help them create onboarding type markdowns that have links to the relevant documentation pages in the Wiki that they want their staff to read in order.

The decision tree idea always comes up b/c every group's use of on campus resources is slightly different and that's ok. If people want us to host an onramp page for their lab, we could consider that, but best that we treat the Wiki as a source of documentation that then groups can pick and choose portions of to create their own onramps.

It's hard enough to coherently document resources here, by mixing in custom requests for content organization, I think we end up making the documentation too hard to manage. Remember: the wiki actually STARTED as a decision tree site (see zingtree.com) that was called "Choose Your 'Omics Adventure" (CYOA). That turned out to be too hard to be the structure for documentation b/c the decision tree wasn't so much of a tree but a maze.

Chilliwack commented 4 years ago

I'm going to close this issue out as there's a lot of ambiguity around what this could be, a past historical attempt (Remember: the wiki actually STARTED as a decision tree site), no real requirements, and pathing data has not been analyzed to understand what are the main paths currently.

I LOVE the idea "OR, if you engage PI's here, you could help them create onboarding type markdowns that have links to the relevant documentation pages in the Wiki that they want their staff to read in order." and would like to try to create a blog post that performs this since "b/c every group's use of on campus resources is slightly different and that's ok"..so I was thinking first completing this; posting it to the blog and then approach some PIs to see if they want a Onboarding blog post specific to their lab that they could routinely point new hires to. This approach would address your concern "but best that we treat the Wiki as a source of documentation that then groups can pick and choose portions of to create their own onramps"

"It's hard enough to coherently document resources here, by mixing in custom requests for content organization, I think we end up making the documentation too hard to manage."... totally!