Hide unfinished features from UI
added in v3
Casper Nielsen
One thing that really stood out when trying the new 2.1 stable release are all the features that are greyed out / coming soon in the Admin part.
It gets you the feeling that it's still a unfinished beta product and not a stable release. It's also bad UI/UX practice to do so.
Upcoming features should be displayed in a road map, not in the production UI as grey-outed buttons and sections.
Nicolas Giard
updated the status to
added in v3
This is fixed in v3. Unfinished features are hidden by default and can be shown via a toggle in the admin.
Chris Gracia
Is this still an issue? I am sitting here wondering how I use these features.
jon r
Indeed this is intruiging for users that don't spend so much time in front of a computer, who will see many buttons that won't work and a lot of extra information that doesn't help right now to get hold of.
Maybe this can be turned into an administrator setting, so site providers have a choice? This leaves space to invite for voluntary contributions and generate interest into the project elsewhere.
Jimmy Trosper
jon r: I'm replying to this a year later, but I absolutely agree. I'm trying out Wiki.js for the first time. I spent a non-trivial amount of time digging through the settings trying to figure out whether I needed to toggle something on, when in fact it's not even an included feature yet, and there's just some bizarre greyed out placeholder button.