Play around with the try instance in different views.
Expected behavior:
Having always a label clearly visible that indicates that I am on a demo instance where the data is not save and that is public and gets reset regularly.
Actual behavior:
There is only a warning on the login page:
Checklist:
I have provided all required information
I am using the latest release or the latest unstable build
**Version information:**
Frontend Version: v0.19.2+14-45defebcf4
API Version: v0.19.2+14-45defebcf4
Browser and OS Version: All
**Steps to reproduce:**
1. Visit https://try.vikunja.io
2. Play around with the try instance in different views.
**Expected behavior:**
Having always a label clearly visible that indicates that I am on a demo instance where the data is not save and that is public and gets reset regularly.
**Actual behavior:**
There is only a warning on the login page:

**Checklist:**
* [x] I have provided all required information
* [x] I am using the latest release or the latest unstable build
* [x] I was able to reproduce the bug on [try](https://try.vikunja.io)
I think that's best built into the api as a "Demo mode" setting. That setting would disable a few things as well on the api side.
Yeah I think we need something like Gitea has:

I think that's best built into the api as a "Demo mode" setting. That setting would disable a few things as well on the api side.
Maybe not as ugly, but yes. I have the feeling that some users don't get that they look at something public.
Also: is it possible to register an account? If so that should probably also be disabled in demo mode.
Maybe not as ugly, but yes. I have the feeling that some users don't get that they look at something public.
Also: is it possible to register an account? If so that should probably also be disabled in demo mode.
Version information:
Frontend Version: v0.19.2+14-45defebcf4
API Version: v0.19.2+14-45defebcf4
Browser and OS Version: All
Steps to reproduce:
Expected behavior:
Having always a label clearly visible that indicates that I am on a demo instance where the data is not save and that is public and gets reset regularly.
Actual behavior:
There is only a warning on the login page:

Checklist:
Yeah I think we need something like Gitea has:
I think that's best built into the api as a "Demo mode" setting. That setting would disable a few things as well on the api side.
Maybe not as ugly, but yes. I have the feeling that some users don't get that they look at something public.
Also: is it possible to register an account? If so that should probably also be disabled in demo mode.
I just realize that we should probably separate the user and pw hint from the demo instance reminder.