You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Bloom user, I want to know when Bloom is down for maintenance.
Background
Currently if we have a period of down time on Bloom backend we don’t have any mechanism to inform our users. They just have a poor user experience and see errors.
Proposal
create a page that tells the user that the site is down for maintenance according to these designs below. We don’t need it to be beautifully accurate. We just need it functional.
It should be turned off and on with a feature flag (see user research banner as an example)
It should override all pages when turned on. i.e. if the feature flag is on. All pages should be redirected to the main
The Nav bar should be just as if one is logged out (i.e. don’t worry too much about what appears)
Under the hood there are a couple of design options. Please choose whichever you prefer:
When the feature flag is on, redirect all users to a /maintenance page. When the feature flag is off, all users are redirected from /maintenance to home page.
When feature flag is on, override the content of whatever the page the user has on. This is so when they refresh and the feature flag is turned off, they return to the same page they originally tried to access.## User story
As a Bloom user, I want to know when Bloom is currently not usable and when it will be back.
Designs
Assets
The text was updated successfully, but these errors were encountered:
User story
As a Bloom user, I want to know when Bloom is down for maintenance.
Background
Currently if we have a period of down time on Bloom backend we don’t have any mechanism to inform our users. They just have a poor user experience and see errors.
Proposal
As a Bloom user, I want to know when Bloom is currently not usable and when it will be back.
Designs
Assets
The text was updated successfully, but these errors were encountered: