When to set up the Internationalization
Permalink
Hi all,
I'm seeking a little best-practice advice on an approach. I've started a new project where I am porting over a site into Concrete5 and will need to utilise the internationalization module.
At the moment, I'm focusing on setting up my pages and everything in the default english without the internationalization module installed with the plan to install it at a later date once we've decided upon the free vs enterprise option.
Could anyone share from experience whether this is an ok approach or would I be building up an issue for later if I have my pure tree set up to then need to bring that all under an /en/ path etc later.
Any advice or tips gratefully received.
Regards,
Dan
I'm seeking a little best-practice advice on an approach. I've started a new project where I am porting over a site into Concrete5 and will need to utilise the internationalization module.
At the moment, I'm focusing on setting up my pages and everything in the default english without the internationalization module installed with the plan to install it at a later date once we've decided upon the free vs enterprise option.
Could anyone share from experience whether this is an ok approach or would I be building up an issue for later if I have my pure tree set up to then need to bring that all under an /en/ path etc later.
Any advice or tips gratefully received.
Regards,
Dan
I don't foresee any major problems, just keep in mind, each language will have its own tree (see the attached image).
Also, this education channel I did on the internationalization add-on may help, when you get started:
http://www.webhostinghub.com/support/edu/concrete5/internationaliza...
I hope this is helpful,
John-Paul