#FeatureRequest
Hello, I mentioned one already, but adding to the #tagged list:
-
see number of clicks on links (optional: Settings > ...)
-
settings, settings, settings :-) && as they grow, an easy 'setup' of pre-configured 'quick settings' templates, with a short description of how they differ/purpose, and recommendation for differing community types, privacy levels. Maybe suggestions of when to consider vs when to avoid. (and still customizable, since it's just a template to help setup)
-
layout options (eventually): hiding sidebars, main column width, mini-view for icons/post row (similar to Discord, for instance), more granular permissions for everything (again, with suggested options in pre-configured setup templates)-- realize stated goal of 'simple', but useful to have & needn't use or bother (via templates), and somewhat inevitable as plugin grows and is used in different situations (in for the penny, in for the pound π), the widgets suggestion below is helpful (especially for early implementations inside different builders, WP dashboard)
-
possible ability for users to distinguish themselves aside from participation & also facilitate payment option (similar to Discord boosting)- whether special avatar/profile customization, extra ability (optional), avail to all... unlock greater features for Community server for all, and incentivize individuals to contribute in this way also (because sometimes one persona will invariably have more to say, and others listen - shouldn't feel compelled to say 'anything' just to participate - 'Boosting' can address this... might call it Hoisting/Lift/Elevate; admin can enable and set/suggest prices.
-
could add command functions (similar to inline @mentions and #taging) for the above #4, and also have common ones. For example, !GO might have a coloured background for the post or some extra feature. And @OWN_USERNAME might email a copy of the written comment to yourself when posted
-
option to reverse feed direction, and include an easily recognizable 'Last Viewed' marker (eg. red line) per each user and channel, that separates older viewed comments from newer unread (available inside feed, without navigating to Notifications > Unread Only)
Without allowing reverse feed, there's a greater temptation to post before looking at older comments (π) and see whether something has already been mentioned/addressed. Also, it necessitates scrolling down (waiting for lazy load to refresh), deciding 'how far back' one want's to read, the working back to the top (most recent comment). Markers could work for both comment direction flows.
