-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
What would go in a site-wide FAQ? #79
Comments
Related question - what else could be in a general site-wide FAQ? |
The text reads well. This could be in an accordion or at the bottom of the relevant page? If not a site FAQ would be good. As for what else could be in a FAQ, we could at least link to particular other FAQs we mention, e.g. the instructor FAQ. However, having a "Carpentries-wide" FAQ might be a really nice addition to the new site. |
Assigning to @OscarSiba as we chatted yesterday about what a Carpentries-wide FAQ would look like. This would be distinct from specific FAQs we already have (for workshops, membership, etc.) |
We have a couple of FAQ pages I can think of (membership, instructor etc). Is there a way to have these linked into a site wide FAQ page |
Yes. Maybe the FAQ could be categorized by Member, Instructor, Trainer, General?? |
Renamed issue because this is about a potential site-wide FAQ rather than just about community profiles |
This we can only really complete once the Handbook is also in place, as some of the answers in a Carpentries-wide FAQ would also link to it, and possibly also to materials to be placed in the Commons. Might be a page worth revisiting in the January iteration of the website. Alternatively we can work towards one to launch at the same time as the Handbook. |
Thanks @OscarSiba |
Toby recommended the following as a FAQ style question on our website, instead of repeating this language across our various profile pages. I think this is an excellent idea. Opening this issue to think about where this should go, since we do not have a general FAQ.
The text was updated successfully, but these errors were encountered: