One Installation with Multiple Sites vs Multiple Installation
Hey dear umbraco family,
I can't explain how I like umbraco, I can't really look into other CMSs although I have some technical knowledge restirictions using umbraco.
I have one project which will be available in several countries (russia, turkey, italy etc.) and what I really wonder is which is better option: to have one installation which covers all sites or have different installation respective to each country.
I was thinking that having all sites in one installation would slow down umbraco and may consume more power for the server. I am planning to use Amazon EC2 btw. Could you please enlighten me regarding pros and cons? I really can't decide with limited knowledge.
Umbraco can handle multiple sites in one installation.
I guess your sites for different countries will all have the same templates and functions. I would recommend using one installation because you can easily reuse the templates and it is also easier to maintain.
Like Dawoe told I would go for a single installation for the same reasons appointed. I don't have much experience with multilangual websites but this pratices might help you.
Node Structure
Have a different node tree for each language and each top node in the tree should have a default culture specified along with a hostname.
For domain entities (e.g. Products) you do not duplicate the nodes but instead use a (global) repository node tree in a different section and offer language specific overrides on the properties (for example on a tab for each language).
For text that is not content (e.g. defined in document types/templates/macros) you should use language dictionaries.
Dictionaries should be well structured to help find entries.
Clients should most of the time be able to edit dictionary items. There exists a package that lets them do so without giving access to the Settings section.
It would be very nice if the client is able to edit the relevant dictionary items while working on a content page, we need to develop a solution for that.
URLs
SEO wise it’s best to use a single domain (.com mostly) and put the language in the URL (e.g. /nl/). You can 301 redirect from a different language specific domain.
Don’t put country or currency in the URL, use browser culture and/or session for that
thanks for pointing out important points. For the URLs; I will go with different domains since each website content and branding will be different but structure will be the same.
I need to setup an installation that will consist of about 200 web sites under one umbraco. Each domain must have their own users, content, products, etc. What are the steps to do this? I've been searching for hours and don't see any step by step instructions on how to get this setup with Umbraco. Any information would be awesome, thanks!
One Installation with Multiple Sites vs Multiple Installation
Hey dear umbraco family,
I can't explain how I like umbraco, I can't really look into other CMSs although I have some technical knowledge restirictions using umbraco.
I have one project which will be available in several countries (russia, turkey, italy etc.) and what I really wonder is which is better option: to have one installation which covers all sites or have different installation respective to each country.
I was thinking that having all sites in one installation would slow down umbraco and may consume more power for the server. I am planning to use Amazon EC2 btw. Could you please enlighten me regarding pros and cons? I really can't decide with limited knowledge.
Best regards,
Umbraco can handle multiple sites in one installation.
I guess your sites for different countries will all have the same templates and functions. I would recommend using one installation because you can easily reuse the templates and it is also easier to maintain.
hey dawoe
yes, using same templates is what I really want. It will also be easy to add new features and make fixes.
I will go for one installation thanks for your answer.
Hey Kadir,
Like Dawoe told I would go for a single installation for the same reasons appointed. I don't have much experience with multilangual websites but this pratices might help you.
Node Structure
Have a different node tree for each language and each top node in the tree should have a default culture specified along with a hostname.
For domain entities (e.g. Products) you do not duplicate the nodes but instead use a (global) repository node tree in a different section and offer language specific overrides on the properties (for example on a tab for each language).
Use Vizioz.Relationships to let the user edit/set/remove relationships between nodes (not necessarily intended for languages). As a plus this package also displays the set culture of the node-set it is in: http://our.umbraco.org/projects/backoffice-extensions/viziozrelationships
Dictionary Items
For text that is not content (e.g. defined in document types/templates/macros) you should use language dictionaries.
Dictionaries should be well structured to help find entries.
Clients should most of the time be able to edit dictionary items. There exists a package that lets them do so without giving access to the Settings section.
It would be very nice if the client is able to edit the relevant dictionary items while working on a content page, we need to develop a solution for that.
URLs
SEO wise it’s best to use a single domain (.com mostly) and put the language in the URL (e.g. /nl/). You can 301 redirect from a different language specific domain.
Don’t put country or currency in the URL, use browser culture and/or session for that
Hey antao,
thanks for pointing out important points. For the URLs; I will go with different domains since each website content and branding will be different but structure will be the same.
best
I need to setup an installation that will consist of about 200 web sites under one umbraco. Each domain must have their own users, content, products, etc. What are the steps to do this? I've been searching for hours and don't see any step by step instructions on how to get this setup with Umbraco. Any information would be awesome, thanks!
What about multiple domains (seperate sites with some shared content) that each have multiple languages? What would the best approach be then?
is working on a reply...