Add 'warning header' feature #205

New Issue

merenber · 2021-08-28T17:56:56-04:00

merenber commented

2021-08-28 17:56:56 -04:00

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.

👍 1

a3thakra added this to the Post launch milestone 2021-08-28 21:46:04 -04:00

a3thakra added the

Feature Request

label 2021-08-30 00:20:08 -04:00

a3thakra added the

Priority - Low

label 2021-09-27 17:05:59 -04:00

j285he added

Priority - High

and removed

Priority - Low

labels 2022-01-06 14:55:46 -05:00

snedadah self-assigned this 2022-01-19 20:50:49 -05:00

snedadah was unassigned by a258wang

2022-01-19 20:51:57 -05:00

snedadah was assigned by a258wang

2022-01-19 22:45:17 -05:00

a258wang commented

2022-01-20 00:20:48 -05:00

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 referenced a pull request that will close this issue

2022-01-30 16:16:26 -05:00

Warning Header (Closes #205) #394

snedadah closed this issue

2022-02-22 23:29:55 -05:00

snedadah referenced this issue from a commit

2022-02-22 23:29:57 -05:00

Warning Header (Closes #205) (#394)

Sign in to join this conversation.