Skip to content

Column data links to trigger filters in back-end tables #1716

Description

@Bloke

In various panels, there's an opportunity to make more items in each row clickable. e.g. on the Articles panel:

  • Click a category name to filter by that category (1 and/or 2?)
  • Click the section to filter by section name
  • Click the author name to filter by author

Considerations:

  • On other panels (e.g. Sections or Languages panel), clicking the numeric value takes you to a different panel and filters the corresponding assets. Here, we're considering filtering content on the same panel, which is inconsistent. People might think that clicking the section will take them to the sections panel to edit the section metadata? So we need to be clear in signposting. A convention is fine. e.g. if the content is in parentheses it will take you to another panel, if not it'll keep you on the same panel. This might be unattainable as it would mean putting parentheses around every value in the Article column on the Sections panel table. And what would we do about the currently linked Status column on the Articles panel, which takes you to the front-end to view the article?
  • When filtering by article category, which do we filter by? Only the corresponding category (1 or 2) depending on what's been clicked? Or filter by both all the time? Or somehow permit both. Also project forward to when we repurpose Keywords as Tags. What will we display on the panel here, and what would clicking a tag (if we permit that or even show the column) do?
  • Some column items already trigger the Edit step (e.g. clicking the article ID or title of any main asset type). This proposal would trigger a different outcome when clicking a 'filter' column, which might be unexpected. The difference is semi-obvious: if the content is in some way unique (as the id/title/filename/image name/etc are) then it triggers the edit step, otherwise it's a filter. But if there could be some visual cue that the actions are going to different (colour, shading, icon, different underline, whatever) then that might be handy.

Lots to think about, but if we're careful and consistent, this can be an asset to back-end navigation and/or content management.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions