Skip to main content

FluentCommunity

#General

Best Practices for FluentCommunity Implementation

Here’s a clearer and more concise version you can post for community input:

I currently have two websites: luisromero.com and training.luisromero.com.

  • luisromero.com is primarily used to advertise Luis's services and includes sales funnels leading to payment options.
  • training.luisromero.com is set up with the FluentCommunity plugin to host all of his training videos.

I’m considering consolidating everything under luisromero.com by installing the FluentCommunity plugin there, so the community would live at luisromero.com/community instead of maintaining the subdomain.

One challenge is that FluentCommunity seems to require the community page to be nested (e.g., /community) and can’t make training.luisromero.com function as the main page of the subdomain.

Should I remove training.luisromero.com and move everything to luisromero.com/community, or is it worth keeping the subdomain for any reason?

This particular community will have little to no actual discussions, comments, or interactions. It's primary purpose is for customers to watch educational videos and download relevant attachments pertaining to each lesson.

Nevertheless, my biggest concern is traffic and the workload it might have on the server.

Looking forward to hearing your thoughts!

  • 1 like
  • 2 comments

Mat ‎

Connery Johnson there are mamy aspects to consider when settings up community.

  • From the maintenance perspective keeping one WP instance might be easier and cheaper.
  • From the integration perspective you might want to manage everything easy with FluentCRM so keeping one WP instance might be easier.
  • From the security perspective you might have two separate instances (two separate hostings for redundency etc).
  • From the workload perspective you might keep two instances so the primary WP instance is not affected by the Community (especially if you want to upload videos and other media file directly to you hosting - you don't want to keep them externaly with R2, S3 or Bunny - video decoding etc is on your hosting end).
  • From the SEO perspective you might have two separate WP instances (two different IP) so you can link from your subdomain or a secondary domain to your primary but it's not worth it if you don't have a related posts/comments in your community (link building strategy to your website but not to other websites etc)
  • If your community has <500 concurent/active users (I am not talking about passive users or a ghost accounts here) it might be not worth it to have two separate WP instances unless you have a HUGE daily traffic (+10k) on your website/store and you send many many automated emails with FluentCRM. It also depends what server you will use.

My granma said: "don't keep all eggs in one basket" but she always had only one fridge. Did she lie to me or she knew that she can buy a new fridge and eggs fast with 1 day delivery and setup.

Note: fCommunity is stored in a separated DB tables and it shouldnt be any issue when the fCommunity is down for some unexpected reason (example: after upgrade)

Note: if you have some advanced caching settings for the main/primary website or you use some advanced plugins/settings (Media offload, Strict Security) then first check if you can achieve your goal when using only 1 WP instance.

Adding related link + link + link + link + link

BTW: if you want to have your community (on a subdomain) without the slug check this post here

Erkan Kilic

Thank you