-
Notifications
You must be signed in to change notification settings - Fork 45
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
Changed title of /query page to manage navigation menu #217
base: main
Are you sure you want to change the base?
Conversation
a5c9f0c
to
0558483
Compare
0558483
to
9f8e4f7
Compare
@sarahboyce Since you've recently made changes on the ticket page, I was wondering if you had opinions ™️ about this. Do you think it's worth changing the title? |
Yes I think so I don't think this will change anyone's life, but I agree with it in principle. We could also call it "Tickets" |
Oh yeah, better!
I feel like "Show Tickets" would be even more accurate as people don't necessarily initially get to view tickets. What they encounter first on that page is a form, which manipulates which tickets are ultimately displayed, i.e. shown. If people know to look for them. :P I for one didn't even immediately realise the tickets were listed below the form all along, which is why I suggested to not use the menu label as heading for the form section of the page:
If the page were set up differently, e.g. if the form were collapsed by default, just "Tickets" would make the most sense, IMO. "View tickets" could be misunderstood to mean the tickets themselves, i.e. the ticket contents, can be viewed directly from that menu. |
Basically, what I'm imagining is the following page structure: Blah blah regular text leading into the filter form... [Form] Headline that mirrors menu label (e.g. "Show tickets")[List of tickets] The introductory line could be really short, its only purpose would be to acknowledge the form/filterability of the tickets, and it'd ideally make reference to the list of tickets below (which I'm guessing I didn't see because the form takes up a bit of space and I was likely looking at it from a browser window with reduced height). Ex. "Filter the list of tickets below:" |
To clarify: I think "Show tickets" makes the most sense with the current page structure (form visible, heading visually grouped with form); "Tickets" would work best as heading for (just) the list of tickets, i.e. if it immediately preceeded that. |
Here's how it looks like: