When we initially built out the Breaking News feature, we decided to focus our designers' time on the user-facing UI, but not the internal edit view. The current edit page, while functional, has a few strange or potential misleading behaviors, so this is a list of things we can change to improve it:
It's easy to mistake the "Add Breaking News Article" button for the "Save" button. I think this could be mitigated in two ways:
Moving the "Save" and "Delete" buttons to the bottom of each form, above the "Add Breaking News Article" button
Changing the text of the "Save" button to "Create" for when we create a new article, vs. leaving it as "Save" when we edit an existing one
Fix API endpoint so that articles without an effective date are still shown. It's confusing to fill out a news article without an effective date, save it, and then have it disappear when you refresh the edit page
Alternatively, make the Effective Date a required field both in the DB and in the UI, so that you can't save if it's not filled in
Some user visible indication that the Save button has actually performed an action. Right now, hitting the Save button doesn't change the UI at all, so the user is left wondering whether it actually saved. Even an alert() call would be fine here.
These are just some things that came to mind, but feel free to edit this ticket with anything else you come up with.
When we initially built out the Breaking News feature, we decided to focus our designers' time on the user-facing UI, but not the internal edit view. The current edit page, while functional, has a few strange or potential misleading behaviors, so this is a list of things we can change to improve it:
alert()call would be fine here.These are just some things that came to mind, but feel free to edit this ticket with anything else you come up with.