Add 'warning header' feature #205

Closed
opened 12 months ago by merenber · 1 comments
Owner

This can be done post-launch - it would be nice to have a banner at the top of the website for machine outage warnings. The warning period should only last a week or so.

Edit from Neil: The approach I think we should take for showing the banner is to specify a start and end date/time, and show the banner based on that. This way, we could also keep historical banners, and pre-schedule banners as well.

This can be done post-launch - it would be nice to have a banner at the top of the website for machine outage warnings. The warning period should only last a week or so. Edit from Neil: The approach I think we should take for showing the banner is to specify a start and end date/time, and show the banner based on that. This way, we could also keep historical banners, and pre-schedule banners as well.
a3thakra added this to the Post launch milestone 12 months ago
a3thakra added the
Feature Request
label 12 months ago
a3thakra added the
Priority - Low
label 11 months ago
j285he added
Priority - High
and removed
Priority - Low
labels 7 months ago
snedadah self-assigned this 7 months ago
snedadah was unassigned by a258wang 7 months ago
snedadah was assigned by a258wang 7 months ago
Owner

Additional notes from our meeting on Jan. 19/2022:

  • The warnings can be stored in .md files in a subfolder under the content folder, similar to how news and events are stored.
  • For now, emit an error at build time if any warnings have an overlap in the time period when they're supposed to be displayed.
  • The warning banner should appear at the top of all pages (similar to how the Navbar appears at the top of all pages).
  • For now, we do not need to display an X to close the banner or anything.
  • We have a form-invalid colour defined in pages/_app.css that currently is not being used anywhere - perhaps this colour could be modified slightly, renamed, and then used as the background colour for the warning banner.
  • We will not submit a formal design request for this feature, however please send a screenshot in the ~website-design channel on Mattermost once the frontend has been implemented, in order to get feedback from the Design team.
Additional notes from our meeting on Jan. 19/2022: - The warnings can be stored in .md files in a subfolder under the `content` folder, similar to how news and events are stored. - For now, emit an error at build time if any warnings have an overlap in the time period when they're supposed to be displayed. - The warning banner should appear at the top of all pages (similar to how the Navbar appears at the top of all pages). - For now, we do not need to display an X to close the banner or anything. - We have a `form-invalid` colour defined in `pages/_app.css` that currently is not being used anywhere - perhaps this colour could be modified slightly, renamed, and then used as the background colour for the warning banner. - We will not submit a formal design request for this feature, however please send a screenshot in the ~website-design channel on Mattermost once the frontend has been implemented, in order to get feedback from the Design team.
snedadah closed this issue 6 months ago
snedadah referenced this issue from a commit 6 months ago
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.