-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Table: Quick-actions #55096
Comments
Where are we on the design aspect here? I wanted to start looking at this soon. |
@youknowriad the latest work includes quick-actions at the end of each row. They are split into two categories; Primary and Secondary. Primary actions are displayed permanently, and secondary actions are grouped in an overflow menu. quick-actions.mp4For Pages the primary actions would be 'View' and 'Trash'. The full list of secondary actions (and their associated UIs) needs to be decided upon, but potentially we can include 'Edit' and 'View revisions' straight away as there are clear destinations for each. For templates, the primary action(s) would be 'Trash/Reset' where applicable. Secondary actions would be 'Edit', 'View revisions', and 'Rename' for custom templates. In both cases there might be an argument to make 'Edit' a primary action, depending on the behavior we settle on for clicking the document title (edit vs. view details). |
@jameskoster Makes sense, how do these actions translate/render in the "grid view"? |
It would be nice to include actions in the same format if possible. Whether they appear adjacent to / beneath the title, overlayed on the thumbnail, or something else will likely depend on how other fields are handled in that view mode. I suspect this will require a dedicated exploration to get right. |
@jameskoster the |
The frontend. It's the same functionality as the "View" link in the current pages list in wp-admin. |
First iteration landed, so it would be good to update this issue with more specific action items, or create a new one. |
@ntsekouras with the foundations in place I reckon we can close this and open issues for different contexts (pages, templates). I'll open those asap. One small detail you may want to address until then: The 'Edit' action should go directly into the editor rather than the details view. |
@jameskoster what do you mean by that? --edit Actually I probably get what you mean. There could be a race condition there and sometimes redirects you to the details view. I'll take a look at it. |
Just to clarify, the behavior should essentially match the wp-admin 'Edit' link, which takes you directly to the editor (no details view interstitial). |
This ticket is a stub to include designs for quick-actions in table views.
"Quick-actions" include things like moving pages to the trash, or reseting a template. Additionally, they can potentially encapsulate much of the "quick edit" affordance on wp-admin tables, IE enabling users to edit post meta without engaging the full-screen editor.
The text was updated successfully, but these errors were encountered: