I'm working with a very big client and I would like to know your recommendations for this scenario:
a. It's a hugge portal with a home page and many subsites for each product (over 80+ minisites)
b. The deploy will be over 3 releases, example: 1st release => 25 minisites, 2nd => 25 minisites, 3rd => 30 minisites
c. Not all minisites are complex, 60 of them only have 2 or 3 pages max
d. The production URL must be: www.generalsite.com
e. The product pages URL must be: www.generalsite.com/product
f. A general header and footer must be on each page, including the home page (hub) and the products pages.
g. There will be roles for each product, to allow the CMS final user to only modify and view certain pages.
h. A breadcrumb must show from home to specific page: home > category > product > page > subpage
i. Is considered to be in more languages.
I was thinking of using only one Sitefinity project to implement this, and make use of page groups to consolidate the product pages.
Also using a single database for the project.
The average users for CMS are 15, and my web server and DB server are powerfull and have growing capabilities.
Only the merge replication makes me have doubts over my desing structure, because the 3 releases.
It is expected to have a large amount of visits to the minisites.
So, what's the Sitefinity Team recommendation??
The Sitefinity DB has any trouble for sites over 350+ pages??
The CMS admin page has any bugs over so much roles or pages??
Is there best practices??
Thanks in advance.