Remove information banners highlighting missing fields #99
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This removes these banners from the course pages and "About your organisation" page:
The intent behind these banners was to highlight actions that need to be taken due to new fields being added to the service for the next cycle of courses. The use the Notification banner component, but with a different header.
In usability research, almost no-one clicked any of the links, and no-one used the banner links to navigate to sections consistently. Instead, participants tended to scroll down the page and noticed the new fields in situ, or attempted to publish the course and saw the same content as an Error summary, which they did notice and interact with:
Our hypothesis is that the blue banner is missed due to "banner blindness" and a user focus on reviewing their course content which causes them to scroll past it.
In addition, the banner is potentially misleading as it only highlights the newly-added fields for attention, but providers will typically want to review all the content at rollover, as some things may have changed – particularly the fee amount.
Removing the banner should cause no negative consequences as we have the error summary as a fallback.
In addition, removing the banner reduces the likelihood of users seeing TWO blue notification banners, if we were to ever add a service-wide banner (eg warning of upcoming downtime).