Rio
Rio
I'd like to take this issue! Just confirming, this would be a warning on this page, right? 
I was thinking of adding it like this so it doesn't get lost in the message history, what do you think? See PR #2794 for a final version of this
This is the dark mode version: 
Also, I am currently using [this](https://assets.stickpng.com/images/5a81af7d9123fa7bcc9b0793.png) as the warning image, however, if there is an internal one that works better I'm happy to replace it.
@andreaskoepf Could we make the message to encourage users to give feedback a new issue since it is not directly related to this issue?
I've synced my fork and it seems like changes were pushed to main that don't pass pre-commit. These errors aren't related to the changes I've made @andreaskoepf I've moved all...
 Here is the new warning to work with the codebase changes The warning image still needs to be added to the internal github storage I believe, so a placeholder...
@olliestanley If there is a specific message you would like to have instead I am happy to replace it!
Sounds good, makes sense to make a separate PR then.
@cesaronly87 Do you mean on the deployed website or when you build internally?