right now, we are using copy in two places:
(1) the function view page
(2) the function edit page
We should determine if we want to keep using these and add them in other object view/edit pages and the creation page, or remove it all together
| • JKieserman | |
| Jul 7 2022, 11:42 AM |
| F35526198: Screen Shot 2022-09-20 at 2.04.06 PM.png | |
| Sep 20 2022, 8:22 PM |
right now, we are using copy in two places:
(1) the function view page
(2) the function edit page
We should determine if we want to keep using these and add them in other object view/edit pages and the creation page, or remove it all together
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • RWambua-WMF | T324613 Copy Related Items in G4 | |||
| Duplicate | None | T312532 Copy: Evaluate each of the bits of informational text in the function view and edit UX, and whether we need them at all or should update them | |||
| Resolved | • JKieserman | T322132 FunctionDefinition: update copy for input fields |
Could you specify which copy? Do you mean:
The third is a placeholder for the documentation work in Phase Iota; the last was one of the bits be agreed with Legal ages ago. The first two are from Aishwarya I believe, but from a long time ago, and we might want to modernise and tighten them as well as use them more consistently.
Or did you mean something else?
I mean (1) and (2). Notably, (2) shows up even if it is NOT a function definition, so that should be changed. @aminalhazwani had mentioned potentially just getting rid of that copy altogether.
To follow up to @JKieserman above, here’s my proposal.
Function viewer (Read tab):
Function editor (Edit source tab):
To answer James’ question:
Generally speaking, since the UI is changing a lot, and since I would suggest to prioritize a self-explanatory UI rather than additional copy, I would like to propose to remove all non-UI existing copy. We can then, as we test the core user journeys, add accompanying help text as necessary.
What do you all think of this proposal?
Looping in also @SWoodruff-WMF as this might touch on her research and design explorations on making features more usable, discoverable, and accessible.
Quick question, on the details tab, does the link "Learn more about the review process.” go anywhere, or is this something that does not exist yet?
"Generally speaking, since the UI is changing a lot, and since I would suggest to prioritize a self-explanatory UI rather than additional copy, I would like to propose to remove all non-UI existing copy"
+1 to all of Amin's comments here.
Some of these can also be resolved or covered by what I'm exploring with Notifications/alerts
For example, on the function definition tab, different states based on user permissions
(and then link to information about different user permissions --- same q as above, is this a real link yet?)
(Or, better yet, don't even show the function definition as editable unless the users has appropriate permissions)
Quick question, on the details tab, does the link "Learn more about the review process.” go anywhere, or is this something that does not exist yet?
My assumption is that it will link somewhere like this https://en.wikipedia.org/wiki/Wikipedia:Reviewing but for Wikifunctions. I do wonder thou if this is the right place to display such content. What if we expose this information in either the registration process, or the publishing component?
- If a user has full permissions, don't show text at all, it'll be clear from the UI what they can edit
Totally agree!
If a user doesn't, and then attempts to change the definition of the function, show notification text that says something along the lines of "You don't have permission to edit function definitions"
(Or, better yet, don't even show the function definition as editable unless the users has appropriate permissions)
+1 also here. The only thing that we might want to explore is the scenario where an editor has (expressed) interest in getting the appropriate permissions. If we show the UI no matter what, the notification might be a good place to redirect editors who desires to get the proper editing rights.
As reported by @JKieserman
After creating a new implementation, I get redirected to the main page and am see a text box that reads “Please add an implementation and a test to see results” but…I just added an implementation. This copy should be more specific to avoid confusion (same thing for tester page). It also isn’t clear what this is referring to.
The whole message is this:
"wikilambda-tester-no-results": "No test results found. Please add an implementation and a test to see results."