We are currently using a third party to translate and maintain Spanish language content for the Spanish version of our website. A project is starting to continue using the third party to translate the content, but we will be storing and maintaining the Spanish language content on-site, in TeamSite. We are not using Site Publisher and it appears that any built-in localization components within TeamSite are specific to Site Publisher - I may be wrong about that but I've done a preliminary search through the docs and I don't see anything useful.
What I'm looking for are any best practices, experiences, do's and don'ts for storing multiple versions of content in TeamSite (Needs to be scalable if we decide to add more langauges in the future). Use multiple branches? Use folder structure within the same branch? We'd like to not change the name of content files based on their language, but use folders to indicate language. We can be swayed from that, though.
If anyone can provide their experiences with building this out in TeamSite, I'd appreciate it.
