Skip to main content

FluentCommunity

#Feature Request

Features suggestion

Sharing list of some suggestions:

  • Admin should be able to encourage users to log in or register an account when fCommunity is Public and users/are not loggedIn by:

    • hidding userNames (instead display a specifies word like "Ninja") and hide User Profiles endpoints/urls (so nobody can access them)
    • hidding comments under posts (only post content would be visible for Public fCommunity) and Spaces (if a user is not a member of that Space)
    • hidding users list for Likes (display number of Likes only and when clicking the list number not logged user/not a member would see a message/popup to log in
    • showing first x characters of posts/comments
    • limit posts/comments preview to x days back (in case searchbox is used display text to log in for more results/lazy load)

  • Allow the Admin to provide CSS class name (text field) next to the color hex# picker so theme colors can be matched with theme colors automatically

  • Admin/MODS could specify posts thread visibility in Public Spaces and change the default post visibility from Visible to Space Members (Privacy Space Settings) to:

    • Visible to LoggedIn Users (for Public fCommunity)
    • Visible to Paid/Premium Users
    • Visible to users with a badge=VIP
    • Visible to Admin/MODS

    This could be useful when the Admin wants to submit a Special Deal/Message/BookingSlot/Post in a Public Space for a specific users group.

  • Admin/Paid/Free Users could call/mention users in posts by a Badge name - (BadgeSlugWithoutSpaces) for example badge=Premium, VIP. Also users could be called by Leaderboard level: L1-L10.
    Users also could called other users by badgeName for example: if they are Paid Users, LeaderboardLevel>2, no restictions

  • When a User Profile completion (100%) requirement is set to obligatory the User Profile is not visible to other users.

    Give also a toggle so Admin can decide (per Space): Only Completed User Profile can join a space and/or submit a post/comment

  • Give the Admin and/or Users ability to configure who can see a User Profile (User Profile Visibility feature), who can see user online status, enable chat (who can use chat: everyone, premium users, uswrs with a specifix badge).

    Also Enable/disable User Profile Page indexing for Public fCommunity.

    In most cases forum administrators disable members profile indexing for spam reason but others wants to promote their users - this should be configurable

  • Ability to say Thanks to other user with transfering own likes (Likes as a fCurrency) so the leaderboard can be more dynamic (No Status Quo)

  • Limit the number of giving likes from one user per day and also see a list of likes from a user just to avoid cheating especially for new accounts

  • Topics/labels could show a number for each topic example: Bug (34) so it would be visible which topic is popular

  • 9 likes
  • 5 comments

Andre Gois

good points

Ceez Vision

I love these ideas.

Shahjahan Jewel

These are great suggestions Mat ‎ But let me respond one by one.

  1. First Point: I think, maybe it will be useful for a few, but there are so many other good ways to encourage members to join. We can build this type of restriction but the problem is, it will make the overall software a bit complicated (Both UX & Code level). I want to keep the whole plugin super performant as well as super easy and simple for the end users.
  2. CSS Class: The whole styling and colors are actually CSS variables bases so anyone can easily customize it in super easy way.
  3. Badge mention: Badges are just a profile attribute, so it's not a classification. Also it's just meta-meta.
  4. Profile Visibility: A good point. We may add that as a feature in the future.
  5. Post thread visibility: It will just add another complexity in the app. The permission should be managed by the space level not a post level.
  6. fCurrency: In the core, we don't want to provide option to alter the points. Points are straightforward numeric calculations of the likes.
  7. Topics/labels Number: Yes, this is something we can add :)

Now, many of you thinking, I am not flexible on many feature requests. It's actually the opposite. Building features are really easy when I have some super energetic engineers, and I am also a coder 🙈. The main challenge is, what to build and what not. It's super important to make these right decisions. The more features we add, the more UI components we will add and more complexities will arise. That's why even BIG companies with billions of $$$, don't ship all the features. Everytime, I see a feature request, I ask myself, will this feature add values to majority of the users? How much complexity it will add? What's the future look like for this specific feature? Man, it's a hard job that I and my team make when comes to these.

But the good news is, As it's open-source, we can provide hooks for edge cases and anyone can extend it and cover the edge cases.

Again, thank you for your thoughts and your contribution to many features are appreciated from the very first.

Mat ‎

Shahjahan Jewel as always I really appreciate the way you and Ninjas oparate.

These are just suggestions as many other ideas to make the product better and you are the Captain here.

I am looking forward for the next updates and features (small and big once).

Newman

I would absolutely love the username instead of full name, and being able to decide which one is used as an admin