-
-
Notifications
You must be signed in to change notification settings - Fork 166
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
Change name of Hmwk Sets Editor and possibly Classlist Editor #1992
Comments
I would argue to make the new name nouns to roughly fit it with the rest of the name of the tools. Perhaps:
|
It seems that the |
For a little while now in develop, in the TOC we've had:
![]() Each time I go into a course on develop (to test or develop something) I see these and I'm not liking them. At first I thought it was just reflex because they are new and different. But now I'm starting to feel that I dislike these for more than just the bias of familiarity. Does anyone feel similarly? With the repeated use of It's hard to think of better names. But I'm going to toss out these and see if anything sticks in the opinions of others reading this. In addition to renaming those three, I renamed ![]() |
I to have had a bit of trouble navigating with the new menu, but still getting use to it. I do like the idea of replacing |
I like your last suggestion best of them so far. I'm okay with replacing "User", it was the "Manger" part I liked over "Roster". |
I think your last suggestion sounds reasonable. I also don't like the "Course Roster" suggestion. That seems to specific when there are more users than just students that are managed on that page, and a roster typically refers to just students enrolled in the course. |
I've lumped a lot of things here, so I should recap:
Do all of these sound like improvements? I don't want to impose my taste; whatever subset of these (or new suggestions) people are god with, I'll open a PR. It sounds like |
I think
sounds good to me. I think going with consistent plurals is a good idea. |
I would be okay with:
|
Any thoughts on switching the order of |
Consistent plurals...except not with "File Manager"? I can't bring myself to like "Files Manager". But I'll do it if we like the consistency. |
Yeah, I don't like |
I'm ok with changing the order that way.
I'll mention that on another branch I am revising Instructor Tools to be
better in several ways.
…On Sun, Nov 26, 2023, 5:50 PM Jaimos Skriletz ***@***.***> wrote:
Any thoughts on switching the order of Assigner Tool and Accounts Manager
(so Assigner Tool is right below Instructor Tools)? Just a side thought,
I do think these will help with some of the minor issues I have had getting
use to the new menu, but won't really know until I use it for a while.
—
Reply to this email directly, view it on GitHub
<https://protect2.fireeye.com/v1/url?k=31323334-501cfaeb-3132feb7-454455535732-e161e7fb00d4c381&q=1&e=a54d7598-4063-45d1-8055-f75ff6753209&u=https%3A%2F%2Fgithub.com%2Fopenwebwork%2Fwebwork2%2Fissues%2F1992%23issuecomment-1827008183>,
or unsubscribe
<https://protect2.fireeye.com/v1/url?k=31323334-501cfaeb-3132feb7-454455535732-8b2ee61f7a34c371&q=1&e=a54d7598-4063-45d1-8055-f75ff6753209&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABEDOADE2QWKJZVJS56KLKLYGPWVNAVCNFSM6AAAAAAYG2LXPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRXGAYDQMJYGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'll throw in another suggestion for discussion: would it be clearer to make the names into actions? e.g. "Manage Users", "Manage Sets", "Assign Sets", "Manage Course Files", etc? |
I like verbs for buttons (basically stay on the same page but change something about the page or submit a form), but nouns for links (go to a new page). |
Changed in #2265 |
"Hmwk" needs to be replaced with a full word. There was discussion about the fact that not all sets are homework, so we should find a different name. Suggestions include "Assignments" or just "Sets".
Also consensus seemed to be that this should be changed from "Editor" to "Manage".
How about:
The biggest implication of this would be to existing documentation. Both internal documentation and custom site-specific documentation refer to the old names, which may make people confused and/or unhappy.
The text was updated successfully, but these errors were encountered: