Opened 2 years ago

Last modified 3 months ago

#19679 new enhancement

Collapsible FAQ items

Reported by: atagar Owned by: atagar
Priority: Low Milestone:
Component: Core Tor/Stem Version:
Severity: Minor Keywords: website easy
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

To make things manageable Stem's FAQ starts with a header linking to the questions. A nicer approach would be for us to only show the questions, with the answers shown when users click on them.

Not hard and no doubt there's lots of examples we can pull from. One note is that our anchor links need to continue to work. That is to say: providing a link to question X should start with it expanded.

Child Tickets

Change History (6)

comment:1 Changed 22 months ago by kishansag

comment:2 Changed 22 months ago by kishansag

Status: newneeds_review

comment:3 Changed 7 months ago by atagar

Keywords: website, easywebsite easy

comment:4 Changed 5 months ago by atagar

Status: needs_reviewnew

Oops, shame on me for not replying to this. Iirc this code contribution was part of a gsoc application a year back. One of the commits modifies the faq a bit and drops one of the answers. Might be a good starting point but needs some work.

If someone picks them up I'd encourage for them to look at what we did for Nyx. If we can adapt that to work with Sphinx that would likely be best.

https://nyx.torproject.org/#faq
https://gitweb.torproject.org/nyx.git/tree/web

comment:5 Changed 3 months ago by eliaspap

You can find a patch ticket here: https://trac.torproject.org/projects/tor/ticket/27564

comment:6 Changed 3 months ago by atagar

Sorry about the delay and thanks for the patch, eliaspap! I was hoping we could implement this by extending Sphinx. For instance, I implemented our present drop down menus by copying Haiku's template (the Sphinx theme we use) and extending it...

https://gitweb.torproject.org/stem.git/tree/docs/_templates/layout.html

I take it something similar is a no-go here? Rewriting our FAQ in raw html no doubt does the trick, but I worry a little that from a maintainability standpoint it's a step back.

Note: See TracTickets for help on using tickets.