This is off topic obviously, but I would like to add my two cents and say that the lasting frustrations with the Discourse UI makes me completely unsuccessful in recruiting my partners and project stakeholders to use Discourse. They all hate the UI, they just can’t use it because it’s confusing by all means, and this inability to set Kanban to be a useful tool only adds to the frustration of those partners who I’m trying to convince to get on board with using Discourse for project management. To get back to the actual issue discussed in this topic, how on earth should I explain the “@” to a manager who just wants to open the settings panel and configure the kanban lists to their likings? It is all these small things that add up and make people completely disoriented as they enter the Discourse space, and they try to leave immediately and ask me not to engage with them within this platform anymore as it wastes their time. I’m helpless in making people excited about Discourse. And to make it worse, for some reason the Discourse team worsens some aspects of the UI instead of improving it, see a recent update here and my critique of it: Now that the topic title is editable by click, I can't simply copy it without entering the edit mode
Btw, if I enter in there @MyCategory (which I did intuitively while trying to understand what the @ does), it does not tell me any validation errors. How is it considered okay to not tell me I’m doing something incorrectly when it is obvious from the programmer prospective, and it can be easily detected when “Saving…” the updated setting value.
Sorry I had to say it all especially after I saw that someone left Discourse and moved back to Discord, which only confirmed by concerns and frustrations with the UI.