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
There are a few things that are somewhat annoying with the status site.
I already mentioned a few other improvements for the site such as #558 that could help, but there are still a few that I would take the time to talk about real quick.
I may provide screenshots of possible mockups I made using manipulation of the site's source code.
Better status messages for incidents
Right now, the system posts the following messages for the following cases:
Site down
In $COMMIT, $SITE ($URL) was down:
- HTTP code: $CODE
- Response time: $TIME ms
Site up
**Resolved:** $SITE is back up in $COMMIT
There are a few issues I have with those messages.
The first one being that you can't alter those messages through i18n changes, which is kind of weird given everything else can be changed.
The next one is the usage of "was" in the down message. It's weird that a status report uses the past sense, which would give the impression that the issue is already resolved, even if it isn't.
Finally is the usage of $COMMIT here also weird.
Not only is the phrase "in $COMMIT" strange to read, but not everyone understands the concept of Git and commits, so this could only confuse them further.
I would propose the following changes:
Site down
[$COMMIT] $SITE ($URL) is down.
- HTTP code: $CODE
- Response time: $TIME ms
Site up
[$COMMIT]**Resolved:** $SITE is back up.
Example Image
This would make the use of $COMMIT more that of a sort of unique ID, similar to how incident reports have unique IDs themself often, including individual reports.
Incident listing
From what I understand and can see in the demo page is only the very last comment of an issue shown, which kind of destroys the purpose of having those pages to begin with.
The purpose of those pages is to list every update and change to an incident, including new messages posted. Only showing the last one - which in most cases would just be the "site is back up" message anyways - is not good.
If not technically possible can I understand this, but if it is possible should the pages list all comments made.
Example image:
Links on incident pages
There is at least one link that confuses me a lot, which is the Subscribe to Updates link.
This link is virtually the same as the View on GitHub link just below it, which makes it completely useless to even have.
From what I know is there no way to provide a URL for automatic subscribing to an issue, so either get rid of that text or get rid of the View on GitHub one since both do effectively the same.
More consistent CSS stuff
I'm not sure how Svelte works, but if possible, consider adding a way to have more consistent CSS classes/entries.
I myself would like to customize some parts of the site beyond the simple "change color" stuff, but this would require to either target the entire object (i.e. the entire <a> tag rather than <a class="clazz"> or find a way to generate and host my own site setup...
So, if possible, add some consistent class names, so that we could further customize the site.
SVG vs PNG
Right now are graphs being made as PNG images. This is all fine and good, but wouldn't it be better to try and generate SVGs instead?
GitHub already supports rendering of SVGs (both links AND directly uploaded ones) in Markdown files and they could probably load faster and be rescaled with little to no quality loss in the end.
It could perhaps even allow you to color them dynamically, allowing more theme customization.
Tho, I do not know how difficult SVG creation vs PNG one would be with your backend-system, but it could be worth a try, no?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There are a few things that are somewhat annoying with the status site.
I already mentioned a few other improvements for the site such as #558 that could help, but there are still a few that I would take the time to talk about real quick.
I may provide screenshots of possible mockups I made using manipulation of the site's source code.
Better status messages for incidents
Right now, the system posts the following messages for the following cases:
Site down
Site up
There are a few issues I have with those messages.
The first one being that you can't alter those messages through i18n changes, which is kind of weird given everything else can be changed.
The next one is the usage of "was" in the down message. It's weird that a status report uses the past sense, which would give the impression that the issue is already resolved, even if it isn't.
Finally is the usage of $COMMIT here also weird.
Not only is the phrase "in $COMMIT" strange to read, but not everyone understands the concept of Git and commits, so this could only confuse them further.
I would propose the following changes:
Site down
Site up
Example Image
![image](https://user-images.githubusercontent.com/11576465/168438953-65b70fc3-d462-4b12-8feb-3bebc71e38d6.png)
This would make the use of $COMMIT more that of a sort of unique ID, similar to how incident reports have unique IDs themself often, including individual reports.
Incident listing
From what I understand and can see in the demo page is only the very last comment of an issue shown, which kind of destroys the purpose of having those pages to begin with.
The purpose of those pages is to list every update and change to an incident, including new messages posted. Only showing the last one - which in most cases would just be the "site is back up" message anyways - is not good.
If not technically possible can I understand this, but if it is possible should the pages list all comments made.
Example image:
![image](https://user-images.githubusercontent.com/11576465/168439888-8bed7744-7a89-465e-a14b-b4fb561b1469.png)
Links on incident pages
There is at least one link that confuses me a lot, which is the
Subscribe to Updates
link.This link is virtually the same as the
View on GitHub
link just below it, which makes it completely useless to even have.From what I know is there no way to provide a URL for automatic subscribing to an issue, so either get rid of that text or get rid of the
View on GitHub
one since both do effectively the same.More consistent CSS stuff
I'm not sure how Svelte works, but if possible, consider adding a way to have more consistent CSS classes/entries.
I myself would like to customize some parts of the site beyond the simple "change color" stuff, but this would require to either target the entire object (i.e. the entire
<a>
tag rather than<a class="clazz">
or find a way to generate and host my own site setup...So, if possible, add some consistent class names, so that we could further customize the site.
SVG vs PNG
Right now are graphs being made as PNG images. This is all fine and good, but wouldn't it be better to try and generate SVGs instead?
GitHub already supports rendering of SVGs (both links AND directly uploaded ones) in Markdown files and they could probably load faster and be rescaled with little to no quality loss in the end.
It could perhaps even allow you to color them dynamically, allowing more theme customization.
Tho, I do not know how difficult SVG creation vs PNG one would be with your backend-system, but it could be worth a try, no?
Beta Was this translation helpful? Give feedback.
All reactions