UX: Improve support in response to brainstorming#1302
UX: Improve support in response to brainstorming#1302ptamarit merged 7 commits intozenodo:masterfrom
Conversation
carlinmack
changed the title
carlinmack
changed the title
|
let's not merge just yet, need to check if you can still send the support req |
|
I think it's okay, I haven't changed any of the keys for the categories so it should work the same, but when we deploy we should immediately create a test ticket (For context I get |
ptamarit
left a comment
ptamarit
left a comment
There was a problem hiding this comment.
Only important feedback about the footer, everything else looks great!
Thanks a lot!
| { | ||
| "key": "file-modification", | ||
| "title": "File modification", | ||
| "title": "Modify files", |
There was a problem hiding this comment.
non-blocking: I'm not convinced that the active wording is making sense, since the field is called "Category" (and not something like "What do you want to do?").
There was a problem hiding this comment.
I changed to active so that we could group alphabetically i.e.
- record deletion
- ...
- user deletion
vs
- Delete a record
- Delete account
- ...
We could also group semantically instead of alphabetically and keep the current titles, however I think "Delete account" is more use friendly than "User deletion" for example. I would be pro changing the label though to "Type of request", "What do you want to do" etc
There was a problem hiding this comment.
I like the "call to action" labels a bit better... I'm not convinced though regarding the sorting.
I think for organization and findability we could
- group the actions/categories (e.g. "Records", "Account", "Report")
- add short description text, so that the input field search could match better the target category. E.g. imagine:
Quota increase
---
Ask for additional storage beyond 50GB for your draft upload
matches also terms like "storage", "50GB".
There was a problem hiding this comment.
I agree that this dropdown is not great, and that we should work on improving it to make sure people choose the correct category.
Let's do this iteratively in some future pull requests.
| <a href="https://help.zenodo.org/">{{ _('Overview') }}</a> | ||
| </li> | ||
| <li class="item"> | ||
| <a href="https://help.zenodo.org/docs/">{{ _('Docs') }}</a> |
There was a problem hiding this comment.
Yep intentional, the docs page is a subset of the overview page
There was a problem hiding this comment.
We should either remove Guides (which is also a subset) or add back Docs.
There was a problem hiding this comment.
+1 for also removing guides
There was a problem hiding this comment.
I'm OK to try to remove guides. (Worst case we can easily bring it back if we think it was useful.)
|
For some reason it won't show the 7th commit from my branch in this PR 😭 |
This section isn't very useful and the information can be found via the help overview
carlinmack
force-pushed
the
support-ux
branch
from
9cad3b7 to
8350e1b
Compare
|
okay, ready to merge :) |
github-project-automation
bot
moved this from In review 🔍
to To release 🤖
in Sprint Q1/2026
4 participants
See commits as they are separate and descriptive