A little advice: multiple product sites, all multi language

Hi all, I've been using Modx for a few months and I need a little advise, as I have gotten to the "out of the box" part of my implementation and not sure what the best practice would be...

I have several similar product websites, and they all have the same look a feel, but each has a domain and product specific content. Each site cross sells the other products. The sites are to also be multi language as we sell the products world wide. So we have 5 products and want to support 5-7 languages. We need 25-35 contexts to pull this off, based on what I have read.

In my research babel seems to be the way ModX supports the multi language sites, but it appears to be for a modX install that is for that one site/product.

FIRST QUESTION: should we have a separate ModX install for each product, and have the 5-7 contexts to support multiple language in each products install of modx?

As of right now we have one install on a server and its got 10 contexts for 10 different sites ( 5 products and 5 other sites that do not need multiple languages)

Second Question (assuming #1 answer was yes): can multiple ModX installs share the same MySQL install? I would guess each product would have a separate mySQL db.

Third Question (assuming #1 answer was yes): Would I just use .htaccess in the root of my apache server to redirect each domain to its appropriate ModX install, or should I employe apache methods to have separate VirtualHost for each product.

Thanks everyone for the post you have posted, I have learned a lot already and only now I have to ask a question I couldn't seem to fine. I really like ModX, as it seems to be the best of breed for now. My background is in windows and mac platforms so sorry if these questions are easy, I'm in uncharted territory.

Hi j3software!

I do not know much about the babel extra, but it was mentioned as very usable extra.
1Q: I dont see any diference between 1 MODx with 30 contexts or 3 MODx with 10 contexts/each. The server usage is quite the same by my expiriance.
2Q: Yes, the MODxs can share the same database, but will need diferent prefixs for the DB table names (modx1_ modx2_ modx3_).
3Q: You can do it both ways, but if all the sites are managed by the same team, then i suggest only 1 modx install and use of ContextRouter and 30 contexts.

As far as tried, i would recomand only 1 modx installation with all the contexts inside (but be careful, the server must be able to take the load of 30 pages!). I'm currently working on a litle extra that will ease the multi context managment for the administrators of the sites, i'll post it when i'll put it on modx extra.

Sumoborac

Sumoborac, Thanks for the reply. Id rather have 1 ModX install and manage it all from there. I will be the only manager of the sties, as once they are setup its unlikely we will make many changes other than SEO tweaks.
I installed the ContectRouter, VERY NICE, no more copying folders and updating index.php and the .htaccess.. wish I would have found a long time ago..

I look forward to your add-on, can you update this thread when its available.. as stated, I have so many contexts already and its about to multiply.. Something as simple as a folder for each site so all the languages contexts could be contained and out of sight would be helpful.

Now there's a feature request - nested contexts! Actually it's already been requested.