-
Notifications
You must be signed in to change notification settings - Fork 49
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
As a new visitor, I want the FAQ section to be more relevant so that I can understand what is on the site and how to navigate. #162
Labels
C: design thinking
Planning and creative thinking about design elements in new features or improvements
C: documentation
Improvements or additions to documentation
T: new change
Adds new capabilities or functionality
Comments
@jwflory Just for the reference, I have moved the FAQ to the end of the navbar. |
Related to unicef/inventory#35. |
jwflory
added a commit
to unicef/inventory
that referenced
this issue
Oct 7, 2022
This commit reworks the Frequently Asked Questions (F.A.Q.) page on the site to include more useful information about the UNICEF Open Source Inventory, how it is maintained, who is responsible for it, how to contribute, and more. This also changes the file from an AsciiDoc to Markdown file because the content inside of the FAQ shortcodes must be Markdown in order to render. Therefore, it does not make sense to keep the file as AsciiDoc when all the contents of the file are written in Markdown. Closes #35. Closes unicef/inventory-hugo-theme#162. Signed-off-by: Justin W. Flory (he/him) [UNICEF Innovation] <[email protected]>
jwflory
added a commit
to unicef/inventory
that referenced
this issue
Oct 7, 2022
This commit reworks the Frequently Asked Questions (F.A.Q.) page on the site to include more useful information about the UNICEF Open Source Inventory, how it is maintained, who is responsible for it, how to contribute, and more. This also changes the file from an AsciiDoc to Markdown file because the content inside of the FAQ shortcodes must be Markdown in order to render. Therefore, it does not make sense to keep the file as AsciiDoc when all the contents of the file are written in Markdown. Closes #35. Closes unicef/inventory-hugo-theme#162. Signed-off-by: Justin W. Flory (he/him) [UNICEF Innovation] <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C: design thinking
Planning and creative thinking about design elements in new features or improvements
C: documentation
Improvements or additions to documentation
T: new change
Adds new capabilities or functionality
Summary
Both Prateek and Milja went to the FAQ page when they were lost, but it did not have the information they were looking for (e.g. how to find information on the site)
Priority
secondary
Category
design
Type
functional
The text was updated successfully, but these errors were encountered: