Update design for Status Page

[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.

[AugustinMauroy]

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.

[ovflowd]

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.

[bmuenzenmeyer]

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

[AugustinMauroy]

FIY: here some docs about customization https://support.atlassian.com/statuspage/docs/create-pages-and-components-in-statuspage/

[ovflowd]

@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:

[avivkeller]

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.

[MattIPv4]

👀 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).