-
Notifications
You must be signed in to change notification settings - Fork 84
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
[FEATURE] drop-down for FAQ #72
Labels
FAQ
About the FAQ
help wanted
Extra attention is needed
question
Further information is requested
visual
Regarding the UI of the documentation
Comments
MaxHillebrand
added
help wanted
Extra attention is needed
question
Further information is requested
visual
Regarding the UI of the documentation
FAQ
About the FAQ
labels
Aug 5, 2019
Yes, we can add something similar to the tip/warning/danger custom blocks and use the HTML details disclosure tag for the output. |
dennisreimann
added a commit
that referenced
this issue
Aug 5, 2019
As requested in #72 this introduces the custom block `::: details` which can be used to initially hide long-form content and first present a summary. In this case the FAQ leverage it to better structure the questions and answers and provide a better overview than the previously used table of contents. Thoughts: Even though I really like the output, my concern about this is that we need to use a custom block for that and the authoring of the markdown does not seem intuitive. IMHO the headlines plus plaragraphs feel more natural. Feedback welcome! Signed-off-by: Dennis Reimann <mail@dennisreimann.de>
dennisreimann
added a commit
that referenced
this issue
Aug 5, 2019
As requested in #72 this introduces the custom block `::: details` which can be used to initially hide long-form content and first present a summary. In this case the FAQ leverage it to better structure the questions and answers and provide a better overview than the previously used table of contents. Thoughts: Even though I really like the output, my concern about this is that we need to use a custom block for that and the authoring of the markdown does not seem intuitive. IMHO the headlines plus plaragraphs feel more natural. Feedback welcome! If merged, this would close #72. Signed-off-by: Dennis Reimann <mail@dennisreimann.de>
dennisreimann
added a commit
that referenced
this issue
Aug 8, 2019
As requested in #72 this introduces the custom block `::: details` which can be used to initially hide long-form content and first present a summary. In this case the FAQ leverage it to better structure the questions and answers and provide a better overview than the previously used table of contents. Thoughts: Even though I really like the output, my concern about this is that we need to use a custom block for that and the authoring of the markdown does not seem intuitive. IMHO the headlines plus plaragraphs feel more natural. Feedback welcome! If merged, this would close #72. Signed-off-by: Dennis Reimann <mail@dennisreimann.de>
dennisreimann
added a commit
that referenced
this issue
Aug 9, 2019
As requested in #72 this introduces the custom block `::: details` which can be used to initially hide long-form content and first present a summary. In this case the FAQ leverage it to better structure the questions and answers and provide a better overview than the previously used table of contents. Thoughts: Even though I really like the output, my concern about this is that we need to use a custom block for that and the authoring of the markdown does not seem intuitive. IMHO the headlines plus plaragraphs feel more natural. Feedback welcome! If merged, this would close #72. Signed-off-by: Dennis Reimann <mail@dennisreimann.de>
dennisreimann
added a commit
that referenced
this issue
Aug 9, 2019
As requested in #72 this introduces the custom block `::: details` which can be used to initially hide long-form content and first present a summary. In this case the FAQ leverage it to better structure the questions and answers and provide a better overview than the previously used table of contents. Thoughts: Even though I really like the output, my concern about this is that we need to use a custom block for that and the authoring of the markdown does not seem intuitive. IMHO the headlines plus plaragraphs feel more natural. Feedback welcome! If merged, this would close #72. Signed-off-by: Dennis Reimann <mail@dennisreimann.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
FAQ
About the FAQ
help wanted
Extra attention is needed
question
Further information is requested
visual
Regarding the UI of the documentation
Is there a way to add a drop down text box?
This might be useful for the FAQ. All questions are displayed in a single line, each has a drop down arrow, and when clicked it reveals the answer to the question. Somewhat similar to how the new wasabiwallet.io does the FAQ. This would make the
[[toc]]
obsolete.The text was updated successfully, but these errors were encountered: