Skip to content

Update design for Status Page #7053

Open

Description

@MattIPv4

Enter your suggestions in details:

👋 Given the incident today, it seems folks have remembered that we have a status page (though it is very rarely used luckily). It'd be good to get the design updated on it to match the theme used on the site where possible.

Status page gives us very limited control, allowing for custom SCSS to be defined that'll apply globally to all pages and the ability to inject custom HTML (and JavaScript) in the footer of all pages.

The current customisations are documented in nodejs/build#2299. Either we get that PR updated to capture new changes, or perhaps documenting those would be better in this repository now.

Activity

  1. self-assigned this
    on Sep 18, 2024
  2. AugustinMauroy commented on Sep 24, 2024

    @AugustinMauroy
    Member

    I don't know what Claudio has planned from a technical point of view.
    But I think it would be cool to have the code for it under app/status. And that it uses Tailwindcss with parcel for build.
    This would make it possible to have a page that resembles the original site.

  3. ovflowd commented on Sep 24, 2024

    @ovflowd
    Member

    I don't know what Claudio has planned from a technical point of view. But I think it would be cool to have the code for it under app/status. And that it uses Tailwindcss with parcel for build. This would make it possible to have a page that resembles the original site.

    We use Statuspage.io and intend to keep using Statuspage.io -- the ask here is to just update the styling and images of our Statuspage.io to reflect more on the Node.js website design refresh.

    As @MattIPv4 wrote in his post, it also allows custom HYML and JS.

  4. bmuenzenmeyer commented on Sep 25, 2024

    @bmuenzenmeyer
    Contributor

    @ovflowd do you have intentions and capacity to do this?? Else we can find another contributor

  5. AugustinMauroy commented on Oct 24, 2024

    @AugustinMauroy
    Member
  6. removed their assignment
    on Nov 20, 2024
  7. ovflowd commented on Nov 20, 2024

    @ovflowd
    Member

    @ovflowd do you have intentions and capacity to do this?? Else we can find another contributor

    I do have intentions, unfortunately just no capacity D:

  8. avivkeller commented on Apr 3, 2025

    @avivkeller
    Member

    Hey ya'll, I'd be happy to take a look at updating the StatusPage.io instance, but I'd need access to Atlassian, which I'm not sure I am allowed to have as a non-infra member.

  9. MattIPv4 commented on Apr 3, 2025

    @MattIPv4
    MemberAuthor

    👀 I'm not sure why you'd need access particularly, until we're ready to push the changes live? All they give us are very limited slots for HTML, and then global styling, as described in nodejs/build#2299. It should be easy enough to test this directly in browser with an extension like Stylus (+ Tamper/GreaseMonkey to inject HTML/scripting if needed).

  10. avivkeller commented on Apr 3, 2025

    @avivkeller
    Member

    Got it! I'll check into some custom styling, but if anyone else wants to take it over, this isn't getting my undivided attention on the website, so feel free to tag-team me out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions