You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once this has been done, we may want to update the release notes for v4.0.0 around the summary change to link to the Design System for an example implementation.
Why
When a summary list has a mix of rows with and without actions, a 'special treatment' is needed for the rows that do not have actions so that everything displays correctly.
Without a clear example of what this should look like, it can be difficult for users to know how to implement this (unless they are using our macros, which takes care of this for them).
Who needs to work on this
Designers, content designers
Who needs to review this
Content designer, developer?
Done when
Example added to the guidance for the summary list component
We've considered linking to the (unpublished) guidance from the v4.0 release notes around the summary list change
The text was updated successfully, but these errors were encountered:
What
Add an example of a summary list where some of the rows have actions, but some don't.
There is currently an example of this in the frontend review app:
http://govuk-frontend-review.herokuapp.com/components/summary-list/with-some-actions/preview
Once this has been done, we may want to update the release notes for v4.0.0 around the summary change to link to the Design System for an example implementation.
Why
When a summary list has a mix of rows with and without actions, a 'special treatment' is needed for the rows that do not have actions so that everything displays correctly.
Without a clear example of what this should look like, it can be difficult for users to know how to implement this (unless they are using our macros, which takes care of this for them).
Who needs to work on this
Designers, content designers
Who needs to review this
Content designer, developer?
Done when
The text was updated successfully, but these errors were encountered: