Domain or subdomain?
I would like to know what's the best way to work with FluentCommunity. My options are:
- Domain | Home page: I could use it as home page of my domain and I'll get something like this: mydomain.com. And I could use a pretty basic theme with pages that I could set to use FluentCommunity templates (frame or full width). With this option probably the style will be limited but everything will be in a single domain.
- Domain | Portal: I could have a regular site and install FluentCommunity to be used in /portal or any other slug. If the theme has its own style or branding, probably FluentCommunity will not look similar. The fonts will be different, the style will look different, even if you use the same color palette. Probably it's the default options.
- Subdomain: Another option is to set the main site in the domain and FluentCommunity in a subdomain like community.mydomain.com. This is how it's used here. It's good but again, the main site will have its own style and the subdomain will be a different site in terms of look and feel.
How are you using FluentCommunity and what do you think about these 3 scenarios?
Here you have some examples:
Here you can see the Option 2 (Domain | Portal):
wptutscommunity.com/portal
As you can see here, the main website looks different to the community, even when they are sharing the same installation. wptutscommunity.com and wptutscommunity.com/portal. Both looks like different websites.
Here we are using the Option 3 (Subdomain):
community.wpmanageninja.com/portal
I couldn't find yet a site using a Domain | Home page, where FluentCommunity is installed on a main domain and set as home page without any slug. If you have some examples of this let me know.
Anyway, what's the best option for you?
Depending on your preference, what do you want to use your site for?
As for me, I am using mine as a social network, so I am using my domain
That's my site
There is no absolute 'best' way to do so. It depends on your goals. I use it on a subdomain community.example.com without any slug. My goal was to serve only the community from a different URL as the main site. Users log in via the main site, though. But the community looks as clean as it can get URL-wise.
"Users log in via the main site, though."
André Daus can I ask you how did you do that?
Ricardo Corai sure. That is a custom development. My main site is Astro and users sign in via BetterAuth. I created a custom plugin that signs users into FluentCommunity based on BetterAuth. It does handle user creation and deletion, too.