-
Notifications
You must be signed in to change notification settings - Fork 46
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
Should we use hugo-quiz to host workbook? #388
Comments
@voborgus might know more about this. |
Integrated with quizdown-js our website: https://innersourcecommons.org/learn/learning-path/introduction/02/ How to implement this:
Will be happy to receive all questions from the workbook in that form as an incoming contribution. Check all types of questions supported by the library: https://github.com/bonartm/quizdown-js |
Looks great! Thank you! |
Wow this is awesome! Is there a commit or pull request that can be referenced to show how it works, too? I took a quick look but didn't see anything. |
https://github.com/InnerSourceCommons/innersourcecommons.org/blob/master/content/learn/learning-path/introduction/02.md that one's got everything in the front matter and the first few lines. Might actually be a quick copy&paste job. Noice me says. |
OK looks like here is the relevant commit. Neat! We'll need to add this into the autogeneration script. |
@voborgus or @tsadler1988 may be interested in doing this? |
Suggest putting the workbook questions at the bottom of the article in a way that is machine-parsable. Then they can be translated and the script has access to them. |
Opened Host workbook on innersourcecommons.org to take forward this work. |
We have learning path videos and articles on the website, but not the review questions of the workbook. hugo-quiz may be a good choice for putting workbook questions along with each article on the website.
We should do a quick investigation to determine if hugo-quiz will work for us. If things looks good then we can plan to do the work to actually get the review questions on the website.
The text was updated successfully, but these errors were encountered: