Choose against the task constraints
An Astera-owned resource list has a title, one-line task summary and format label; its only action is opening the detail page. A second staff list allows choosing a record and editing its owner, which is a different interaction. The two lists should not be forced into one generic component.
| Condition | Whole-item detail link | Separate detail action |
|---|---|---|
| One navigation action | Title and summary share one useful target | Can add an unnecessary extra target |
| Several record actions | Do not nest editable controls inside a link | Name details and edits separately |
| Meaningful destination | Accessible name should identify the resource | A generic repeated details label needs context |
Make the complete single-action resource item a detail link. On the staff list, separate record navigation and edit actions. The dedicated page carries the complete conditions and relevant download or implementation action.
Actions determine the structure
| List | Available actions | Chosen structure |
|---|---|---|
| Resource library | Open resource | One complete item link |
| Work queue | Open; select; change owner | Separate named controls |
| Static comparison | Read only | Ordinary structured content |
Should the owner selector be nested inside the work queue’s whole-item link?
Show the worked answer
No. It has its own action and must be independently operable. Preserve the record context and provide a separate detail link.
Check the chosen interaction
- Keyboard focus identifies the complete single-action item.
- Interactive controls are not nested inside a navigation link.
- Every catalogue detail link leads to its correct resource.