Skip to main content

Feature requests ranging from basic necessity to game changers

  • WooCommerce integration / ecommerce plugin intergration. This one should be a no-brainer.
  • Integrations with more established plugins in general. I realise the fluent ecosphere wants to develop their own products, but short of rebuilding everything that already exists from scratch, a lot of plugins out there already do certain things and have for years, and integrations would marry useful products together.

Themes & customisation:

  • More flexibility in customising the look of the platform. Currently, the platform looks great and modern but it's one dimensional and there's no way to impose your own look and website feel to the community section. No way to change fonts, layouts, etc.
  • I don't know if it already is the case, but shortcodes galore. This would work especially well for FSE themes or other page builders, allowing you to build your own look and structure for the community I really mean that spaces in general should have shortcodes, but then being able to have individual shortcodes per space would also be brilliant. Shortcodes for widgets, etc.
  • Separating the courses from the community: I personally would prefer if the courses didn't look as though they're part of the community, because the community section can be for chats, etc, for a specific purpose, whereas the learning section, is for the learning section.
  • Possibility to re-arrange the look of the profile: users could be able to choose between different profile layouts, it would create extra incentive to update and complete their profile.

Courses & Community:

  • Automatically adding course members to the course's respective space if there is one, and assigning a space to a course. Since courses and the community are part of the same plugin, would it be possible to have a space dedicated to a specific course, and either only be visible/accessible to only the people who are also part of that course, or only the people who have taken/are completing the course can join the group.
  • Anonymous publishing: making it possible, via a toggle on or off button, to let members publish anonymously in spaces. The content could be traced back to the user by the admin, but wouldn't appear on their profile, unless they could claim it back/switch back the published content to show who published it, and would otherwise not show their username.
  • Editors and admin activity updates (i.e blog posts) showing up on the main feed. If the admin publishes a new blog post, there should be an automatic, though customisable notification showing in the community itself, on the main feed. It could be located on or under the banner section, but would essentially update itself when there is a new publication.

That's all I can think of right now.

William Beem

It's an interesting list, but I definitely do not want anonymous publishing. To me, that's a recipe for disaster.

erisf

William BeemΒ it would definitely be voluntary/the admin could turn the feature off, and track back anyway who published the post even if it's anonymous.

William Beem

erisfΒ It doesn't hurt me at all if the feature is there, so I'm not opposing it.

Sophia S

Great features @yumiifmb. Meanwhile, I added another list here https://community.wpmanageninja.com/portal/space/community-meta/post/course-feature-request-1
Seems like Shahjahan JewelΒ didn't see it as many other posts had been added.

Surely linking a Course to a space is a game changer.....

Thanks for posting:

  • Woo Integration: Currently, you can use FluentCRM or any automation plugin to control the space or course access on Woo activity. We will not have any direct integration for monetization.
  • "Integrations with more established plugins in general": Not sure what do you mean. Example please.
  • Themes & customization: Our team is working on this feature and we are calling it as "Theme Compitability".
  • Automatically adding course members to the course's respective space: You can do that currently with FluentCRM automation (Free)
  • Anonymous publishing: We may never build such a feature. It will create lots of technical complexity.
  • Editors and admin activity: The current feed is only from FluentCommunity data. the regular post and post meta are not included in the feed. But programmatically, you can push an activity on the feed.

Thanks