Feature Requests Support markdown in status page description

Completed

Allowing markdown in the status page description would allow for easy formatting of the status page header. With bullet points, link, bold, etc.

This would make it easier to make readable and properly formatted messages, like:


## 2025-02-12

Short downtime for server rearrangement.

- Expected start time **18:00**

## 2025-02-11

Major maintenance event.

Thomas Jensen
Created on February 12, 2025 · Last update on February 11, 2026
13 Comments
Adrien Rey-Jarthon
Changed status to Completed

You know what? Good idea, done. Basic stuff only though, especially with the horizontal centering some stuff will look weird (lists, tables, etc..) but feel free to try them ^^

Like   Feb 12, 2025 17:31
Thomas Jensen
In response to Adrien Rey-Jarthon

Adrien Rey-Jarthon This absolutely works, thanks Adrien :)

Like   Feb 12, 2025 18:37
Adrien Rey-Jarthon
In response to Adrien Rey-Jarthon

Thomas Jensen Perfect 👌 You're welcome!

Like   Feb 12, 2025 20:44
Thomas Jensen
In response to Adrien Rey-Jarthon

Adrien Rey-Jarthon Hello again. I have tested a bit more, everything works, apart from external images. They get blocked by CSP:

Content-Security-Policy: The page’s settings blocked the loading of a resource (img-src) at https://blog.cavelab.dev/img/me-2x.png because it violates the following directive: “default-src 'self' 'unsafe-inline' data: https://updown.io https://*.updown.io https://www.paypalobjects.com https://cdn.headwayapp.co http://headway-widget.net”

I totally get why it happens. Just FYI.

Like   Feb 13, 2025 12:35
Adrien Rey-Jarthon
In response to Adrien Rey-Jarthon

Thomas Jensen Good point, thanks for testing this! I only tested with images from my domain so I forgot about this ^^ (which is a +1 for CSP)

It's probably best for now though, as I am not comfortable letting anyone add any images here (hope for the best, plan for the worst). I'll remove the "image" mention and re-evaluate this CSP if people ask for it (in a new suggestion).

Like   Feb 13, 2025 15:49
Thomas Jensen
In response to Adrien Rey-Jarthon

Adrien Rey-Jarthon Indeed :) I agree, one value a do see with images is the addition of a logo. But you already have a suggestion for allowing the upload of a logo image1, which is probably a better (and safer) alternative.

Like   Feb 13, 2025 21:28
Adrien Rey-Jarthon
In response to Adrien Rey-Jarthon

Thomas Jensen Indeed, also if using markdown, the logo would end up under the title, centered and not easy to resize so that's only a wooden leg.

Like   Feb 13, 2025 21:45
Thomas Jensen
In response to Adrien Rey-Jarthon

Hello again Adrian, I'm testing this now with badges from healthchecks.io, and that works. Is this intentional or accidental? :)

1 Like   Feb 11, 2026 10:51
Adrien Rey-Jarthon
In response to Thomas Jensen

Hello Thomas! (and welcome to my new feature suggestion board ^^). This is intentional indeed, with the recent addition of comments on the blog and this very feature request board, I reviewed the CSP rules and allowed https image sources. I'll add the note about images being supported to the markdown note soon, thanks for the reminder!

1 Like   Feb 11, 2026 11:18
Thomas Jensen
In response to Adrien Rey-Jarthon

Nice! Yes I did notice the new feature board, I like it :) And using healthchecks.io badges on the updown status page means I can also show status on internal services. Which is very useful. Thanks again, and keep up the good work :)

1 Like   Feb 11, 2026 11:20
Adrien Rey-Jarthon

Perfect then, you're welcome :)
The new board was deployed yesterday I did not even add the "new" tag yet 😅 as I was making sure everything is working well first. Thanks for being the first external tester 👍

1 Like   Feb 11, 2026 11:24
Thomas Jensen
In response to Adrien Rey-Jarthon

Oh... That was purely incidental on my part :p I didn't really notice at first, I just navigated to Feature requests, found the markdown request and started writing. It was easy to find, as it was highlighted as having my vote. So very low friction. Good user experience over all :)

Like   Feb 11, 2026 11:30
Adrien Rey-Jarthon
In response to Thomas Jensen

Glad to hear that! thanks :)

Like   Feb 11, 2026 15:13