Hi there:
Do you believe it be best practices, similar to a buddypress theme, to just add a brand new site with its own theme (or copied them) for each individual membership site?
It seems like the managing of all the content and pages would be a snap compared to doing different access levels on one site for different pages etc…
For example, I am have a general site a that is general consulting related and have membership levels for that site, but all have services or products in different categories where I also may want a whole different set of membership levels and content (but it is sponsored or coming out of a parent company/site…like the general consulting site.
For example:
Parent Company/Site with Membership content levels of its own that are protected).
Sub-Membership Sites with membership content levels of its own that are protected (may be purely membership with a login portal but also may have some public facing content as a normal website too).
—Real Estate Professional Investors Buyers
—Real Estate End User Buyers (not pros)
—Real Estate Sellers (all types)
—Live Futures, Equity, and FX Trading
—Private Investment Capital ROI
—Ministry and Humanitarian website
—Etc.
How would the databased look and be used (all in one or multiple). There are two was I was thinking about doing it…(1) just with a subpage and create a new theme for it with multisite but leave the domain name the same as the parent or (2) make the home of the new sub membership site a subpage but domain map to it with a fresh new domain name for SEO purposes and to have a clear divide between it and the parent/site for portability reasons on several levels. Would the database info be in the parent database or separate etc. Ease of managing multiple etc.
Pros and Cons?
Each sub membership site may have its own buddypress forum, support, etc too.
I noticed some of how incsub.com seems to do it but more insight of how would be great…just want everything tightly integrated, easy to manage, and easy to spin off a membership site in the future if needed (i.e. sell it or move it to a different host independently etc).
Wouldn’t this be better than trying to manage lots of pages with independent membership access levels for different purposes within just the one parent company/site?
Or, should I just manage the pages properly and create all the different membership level inside the parent/site because everything would be all in one place. Then, only if a warranted later create its own domain etc.
I just am looking for simplicity, ease of management, and fast implementation upfront and in the future as further service/product ideas take shape.
Any insights and links and best practices appreciated.
:slight_smile:
Greg