Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Beta" flag for unstable/confusing features #1667

Open
linusha opened this issue Aug 2, 2024 · 0 comments
Open

"Beta" flag for unstable/confusing features #1667

linusha opened this issue Aug 2, 2024 · 0 comments
Labels
✨ enhancement New feature or request 💬 ideas welcome For feature ideas where more input on design decisions and conrete direction are warranted.

Comments

@linusha
Copy link
Contributor

linusha commented Aug 2, 2024

We know of some features which are half-baked, but nevertheless sometimes useful (such as the minimap) and also we have some things that are confusing (such as the morph menus), but require larger amounts of thought and work to get right.

I propose the implementation of a "beta" or "advancedUser" flag, that will allow usage of these things and, when not set, will hide the corresponding UI elements as well. This way, we can make the UI easier to get into for newer users (as lively.next can be "a bit much" in the beginning in any way).

This flag should be stored in the browsers local storage or in the localconfig and it might be handy to toggle this via the dashboard, similar to the fastload/slowload toggle.

@linusha linusha added ✨ enhancement New feature or request 💬 ideas welcome For feature ideas where more input on design decisions and conrete direction are warranted. labels Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ enhancement New feature or request 💬 ideas welcome For feature ideas where more input on design decisions and conrete direction are warranted.
Projects
None yet
Development

No branches or pull requests

1 participant