💡 Unified FluentCart Dashboard on the My Account Page
Over the past few days, several conversations around "profile unification" have shown how fragmented the current user experience can be when combining different Fluent products.
Here's the approach I'd like to propose: a unified FluentCart dashboard displayed on the My Account page, acting as the central hub for all user activities — and working seamlessly whether a site uses FluentCommunity or not.
🛠️ 1. For sites without FluentCommunity
I believe the FluentCart dashboard should become the default user dashboard.
Furthermore, webmasters should be able to:
- Add FluentSupport and FluentAffiliate as optional subsections/tabs (just like on FluentCart's own site, with "Support Tickets" and "Affiliate Dashboard").
- Add fully custom subsections/tabs (even as the first one) using the block editor, shortcodes (
{first_name},{plan_name},{plan_end}, etc.) and conditional logic based on FCRM tags.
This would give full control to build a personalized dashboard that fits each site's unique structure and purpose.
🧭 2. For sites with FluentCommunity
I strongly believe the user's community profile (/portal/u/) should stay focused on community-related content only, with no extra unrelated tabs, since the main purpose of this profile is for other members to visit and interact with it.
I suggest using the top-right avatar popup as the central navigation point, with two or three default links:
- My Account → FluentCart dashboard (with optional Support & Affiliate tabs inside).
- (optional) My Community Profile →
/portal/u/(or as a subsection/tab in the unified dashboard) - Logout.
It means that I would remove "My Spaces" and "Bookmarks" from the avatar popup at the top-right corner of the screen (if they're here by default). They are purely community-related, so they should only belong to the user's community profile page (/portal/u).
Finally, if some webmasters still want to add custom links to the popup — for example, to add direct links to Support Tickets or the Affiliate Dashboard — that's already possible anyway.
🧠 Why this works
- Gives site owners the flexibility to structure the user account page so each use case can find what it needs.
- Provides users with a clear, unified entry point to manage their profile, payments, support tickets, and affiliate activity.
- Keeps account and community management (when there is one) clearly separated.
📸 Mock-ups included (in the comments)
- A mock-up of the My Account homepage.
- A mock-up of the Support Tickets tab as part of the unified FluentCart dashboard.
This proposal is meant to bring coherence without removing flexibility. A single FluentCart-based dashboard could serve as the common ground for all configurations, with community elements clearly separated but still easily accessible.
Shahjahan Jewel Raiyan Marzan Tawsif Ahmed Riyad Faizus Saleheen Mahmudul Hasan Arif :
I believe the team might already be working on something in this area, but since I have no idea what direction is being taken, I wanted to share this vision as a potential contribution to the discussion.
What do you think about moving toward this kind of unified structure?
Every baked-in dashboard ends up limiting those who think beyond the default use case. I’d rather have open dev access and build my own using the provided fields. A basic dashboard for everyone else is fine — as long as it doesn’t block those who want real flexibility.
Andre Daus Many people strongly disagree with you.
I expected disagreement — that’s usually a good sign. Most people prefer ready-made dashboards, and that’s fine. But real progress comes from keeping the system open for those who want to push beyond the default. Convenience and flexibility can coexist — if we design for it.
Andre Daus Disagreement because your reply only represents yourself, a dev, dismissing the vast majority of Fluent users.
Andre Daus but I think we all agree on your conclusion: Convenience and flexibility can coexist — if we design for it.
Laurent Fa That’s funny, because Shahjahan mentioned in the last video that most of their clients are agencies. Agencies live on client requests — change this, adjust that. Flexibility isn’t a nice-to-have; it’s essential.
This video was for the VIPs.
I don't see where my suggestion lacks the flexibility you're talking about. Read it again and you'll see this is to help various use cases for people with no dev skills, which is the majority of WP users whether you like it or not.
Should I also remind you the moto of WPMN which is to help small businesses, therefore many more actors than agencies only?