Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create maintenance page #413

Open
swetha-charles opened this issue Nov 2, 2022 · 1 comment
Open

Create maintenance page #413

swetha-charles opened this issue Nov 2, 2022 · 1 comment
Labels
complexity: advanced Time needed to do this ticket will be large e.g. 2-3+ days feature/enhancement New feature or request help wanted Extra attention is needed
Milestone

Comments

@swetha-charles
Copy link
Contributor

swetha-charles commented Nov 2, 2022

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

  • 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:
    1. 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.
    2. 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

Screenshot 2022-12-29 at 16 34 56

Screenshot 2022-12-29 at 16 34 51

Assets

securicray copy

@swetha-charles swetha-charles added the complexity: moderate Time needed to do this ticket will be moderate e.g. 1-2 days label Nov 2, 2022
@dorkele
Copy link
Contributor

dorkele commented Jan 12, 2023

Picking this up :)

@dorkele dorkele self-assigned this Jan 12, 2023
@eleanorreem eleanorreem added feature/enhancement New feature or request complexity: advanced Time needed to do this ticket will be large e.g. 2-3+ days and removed complexity: moderate Time needed to do this ticket will be moderate e.g. 1-2 days labels Sep 7, 2023
@kyleecodes kyleecodes added this to the 02. Roadmaps milestone Sep 28, 2023
@kyleecodes kyleecodes added the hacktoberfest Hacktoberfest issues label Oct 3, 2023
@kyleecodes kyleecodes removed the hacktoberfest Hacktoberfest issues label Nov 3, 2023
@kyleecodes kyleecodes added the help wanted Extra attention is needed label Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: advanced Time needed to do this ticket will be large e.g. 2-3+ days feature/enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

4 participants