Skip to content
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

Is "Set" the right term? #78

Open
stevejburge opened this issue Dec 14, 2023 · 2 comments
Open

Is "Set" the right term? #78

stevejburge opened this issue Dec 14, 2023 · 2 comments

Comments

@stevejburge
Copy link
Member

We normally use "Assign" for similar actions, for example with taxonomies

We also use "Assign" in the tooltip

Screenshot 2023-12-14 at 12 01 42 PM

@agapetry
Copy link
Contributor

agapetry commented Dec 18, 2023

@stevejburge Assign is there in the tooltip as a synonym for further clarification. Changing the caption to Assign would be reasonable. Here's why I would still prefer Set:

  • Assign is much more awkward as a Post Editor button label: "Set to Proposed" vs. "Assign Proposed"
  • Set seems to suggest a more fundamental property, which Post Status is. We can Assign any number of categories or authors, but Set a post type, post date or post status.
  • For Permissions Pro / Capabilities Pro, we already have support fixed syntax capability names "set_posts_approved", "set_pages_assigned" etc.

@stevejburge
Copy link
Member Author

@agapetry Thanks. I've added some of these to a future release (1.3) so we can see how users react to these, and possibly come back to this later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants