improving feedback board: introduce tags/markup for modules/functional aspects requests relate to (in "topics")
I was just tempted to do a collection-feature request, bundling up existing ones to get a better overview/feel… when I realized: this should actually be part of the board structure. 💡
I think it would improve the efficiency, overview and also cunduciveness of the feedbackboard a lot, if there would not only be tags (topics) for "Bug", "Feature Request", "Improvement" but also for certain aspects/modules of Capacities for which a post is relevant.
E.g.: Graph, Metadata, Appearance/Design, UI/UX, Tags, Journaling, Long Form Writing … etc.
Advantages:
• one can get an overview of what is already proposed; this also would probably improve alignment/formulation of new requests (we all know, most/many people do not do "search by hand", plus search is a bit fiddly in the new system…)
• helps in doing some clarification work as to scoping requests (not bundling different requests into one etc.)
• one gets an idea which aspects of Capacities need most work/improvement; helps also cultivate collective thinking/grasping of the Capacities architecture… which again leads to better proposals, potentially
• would invite browsing the forum, also to get impressions/ideas about Capacities system
• just practical for everyone: team, users, people interested…
0 Comments
Sign in to comment
No comments yet. Be the first to share your thoughts!
