24 july reports content

[Kateharries]

No description provided.

[samuelhwilliams]

Breakdown of changes

Reports homepage

Before	After

• 'Add another' button made secondary and moved below the list of reports. This is to de-emphasise the action. It feels like the primary action for the page only if you don't already have reports. Most of the time, if you have a report, you'll probably be looking to deal with that rather than create a new report.
• Show the user's email instead of name for created by/last updated. Fix the date format to the standard content design format.
• Delete action for a monitoring report now shows a red notification banner with a destructive confirmation button.

Manage monitoring report

Before	After

• Remove all references to sections
• Replace the 'delete' action with a 'manage' action. The manage actions is for renaming and deleting the task.
• "Add task" link becomes "Add another task" if you have tasks.
• "Manage task" -> "Add questions" / " questions".
  • The 'before' manage task page did both task renaming, task deleting, and adding questions. We've now split the rename+delete into a separate 'manage task' page, linked on the right. And we have a 'just show me the questions' page for a task, which the ' questions' page will link to.

Manage task and questions

Before	After (manage task)	After (questions)

• The red 'Delete task' felt like the most prominent action on the page - but actually it's probably the least-likely-to-be-used action here.
• The 'Change name' action is in a standalone summary list - there's no "value" for the "key" (task name), so a bit of a misuse of the component.
• We tried to move the "Delete task" action into the summary list actions, but it felt overloaded and complex.
• A slight feeling from me that doing task renaming, task deleting, and managing questions (which come with a lot of complexity) felt like it overloaded the page.
• So we split this in half:
  • "Manage task" is about the task itself - renaming and deleting
  • "Manage questions" page for adding/editing/reordering questions.
• Removes the 'delete' action from each question row - moved that onto the question page. To minimise links on this page and keep the actions a bit cleaner - with the move up/down links it gets a bit congested.
  • If form builders are deleting questions ALL OF THE TIME, then maybe we lift 'delete' back up. But I think they will be able to tolerate going into the 'edit question' page to delete questions for quite a long time.
• For each question row, we've added the data type into the middle. This is to give the summary list a "value" for each question, which the component wants/needs.
  • We aren't sure on how useful this is - but don't have anything else obvious to put here. Having nothing doesn't feel great for the use of the component/accessibility software might create a confusing experience from having nothing there.

Deletion notification banners

Before	After

• Removed the red destructive buttons as the main action for initiating the delete of a task or question
• Used red links - lower visual prominence on the page, still visible, indicates destructive action.
• These now lead to red notification banners instead of blue.
  • Small technical justification - the "delete" action needs to be a POST request, which generally means button. Design System does not have a way of making buttons look like links, so we use buttons.
  • Destructive red buttons feels sensible to use for the destructive action. These looked odd in a blue banner, so we switched over to a red banner that keeps the colouring+styling consistent.
• Started using these consistently across the prototype for deleting reports+task+questions.
  • There's a feeling that we might want to change this in the future. Maybe questions are small enough to not need a confirmation banner; maybe reports are too big to just use a banner and should have a full interstitial confirmation page. For a future design iteration.