Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It only takes a minute to sign up.
Sign up to join this community
We are setting up a small site with multiple languages, for example, mycompany.com/en/en, mycomany.com/fr/fr, etc. It is very convenient to setup one publication for this, since there aren't that many pages.
However, I can't make use of Tridion Translation Manager if I set it up as one publication (can I?). Any suggestions on how to handle this?
Tridion Translation Manager requires separate publications. I expect your initial convenience of only having to set up one publication would not turn out very convenient after a short while, but you can of course always copy-paste translations around. :)
The Blueprint facilitates localization and translation in Tridion. You certainly can dump all your pages into one publication, but, as Lars mentions, this setup will bite you hard not too far down the road.
It seems that what you are looking for is a way to manage your website pages in one publication. A common practice is to setup a main (master) publication to manage your website regardless of language (e.g. In your company's default language), and have child language publications inheriting the site structure and pages. You would also keep the content in separate Content language publications higher up the Blueprint. This enables working and localizing content separately, while keeping your site structure and pages the same across languages. So in essence, manage local content, but one (main) website.
Here is an illustration: http://www.tridiondeveloper.com/wp-content/uploads/2013/10/classic-blueprint.png
There is even a feature in the publishing dialog allowing to publish child pages down the Blueprint, so that you don't have to navigate across publications to publish - simply do it all from the master website pub.
