I'm working on a Statuspage deployment right now and having a great time. While pretty straight forward to deploy, it does make an organization stop and determine what info needs to be shared and when. Does your organization use Statuspage? If so, show it off and post here so we can all admire!
Oh, I'd show off my work but it's still in private page mode right now so sadly "no can share". :-(
~~Larry
PS. What's Statuspage? Check it out here (click the "See how" link)!
Outstanding @Sophie Reynolds ! - URL?
Larry - we started off with displaying only critical services but it quickly grew adding more components. What I would say is if you do include a lot of components use a small number of component groups so that the page isn't swamped and users can see the past incidents without having to scroll down the page too much. Have fun!
Long term Statuspage customer here and huge advocate (guest wrote this blog post, and was fortunate enough to have 2 pages in the Incident Management Handbook published by Atlassian).
To date, I have deployed 25 public facing Statuspages, which can all be found at Symantec's Status page (division of Broadcom) https://status.symantec.com which is custom built by me using the Statuspage API. Fun fact: Atlassian loved our landing page so much, it inspired them to rebuild theirs at https://status.atlassian.com).
I've been heavily involved in Symantec's incident communication strategy and we're embarking on a new journey to integrate the Statuspages into our products via the new embed widget.
Love to see more pages andI'm happy to share my knowledge and experience with anyone who is new to deploying Statuspage (or anything incident management related).
Cheers,
Nick
Thank you @Nick Coates ! I've been seeing your name a bit as I've dug into the Statuspage area of the community. Appreciate the offer of assistance!
And you're right - there is an odd similarity between the Symantic and Atlassian primary status page. Like the "float-up" affect on yours!
Cheers!