I have a CouchCMS site in English that needs another language added (Spanish). The English version currently has the following sample structure:

- http://example.com
- http://example.com/page-a/
- http://example.com/page-b/
- http://example.com/page-c/
- http://example.com/page-c/category-1/item1.html
- http://example.com/page-c/category-1/item2.html
- http://example.com/page-c/category-2/item-a.html
- http://example.com/page-c/category-2/item-b.html
- http://example.com/blog/

For SEO-purposes, the original link structure has to remain unchanged. The Spanish version should be hosted under a sub-folder (es), but should exclude the blog page, which should not be translated:

- http://example.com/es/
- http://example.com/es/pagina-a/
- http://example.com/es/pagina-b/
- http://example.com/es/page-c/
- http://example.com/es/pagina-c/categori ... eto-1.html
- http://example.com/es/pagina-c/categori ... eto-2.html
...

The site contains some portfolio items categorized in named folders, that need to be translated as well, as you can see from the structure. If a page is not available in Spanish, the English original should be served as the default.

A language switcher should be used to changed between the versions.

Would appreciate your advice on how to approach this in the best way.

[trendoman]

Would appreciate your advice on how to approach this in the best way.

Would you please be more specific about what your trouble is exactly? The best way is usually the one that works for you and makes you happy

If you want anyone else think about your project in some freestyle manner without setting a clear direction, then it comes to a dialogue when every party backs up claims with something.

For example, you approach a complex task and already made some essential choices which will lead to a very narrow way of implementing those choices. Why are those choices made with new url structure - is it a thoughtful decision? I didn't see any explanations in your post.

As to SEO, that can be resolved with permanent redirects, if url structure needs to be redesigned.

So, brother, be more specific and we try to help you or allow us to express ourselves and don't establish arbitrary boundaries. Do you think you can have a little respect to supporting people here?

Lol, you have a lot of free time @trendoman right? You should think before you write...

A simple pointer to the official documentation that does not seem to cover how Couch implements a multi-language website, would have been sufficient.

[trendoman]

Lol, you have a lot of free time @trendoman right? You should think before you write...

A simple pointer to the official documentation that does not seem to cover how Couch implements a multi-language website, would have been sufficient.

I beg your pardon? I wonder who's gonna run and bring you served what you ask for.
You better search forum before getting old waiting. There's a multitude of topics covering different aspects of multi-language templates.

[KK]

@JD,

Exactly an year back, we two had discussed this very topic - viewtopic.php?p=18928#p18928

I think, that is still the right solution.

You can use the original 'separate folder for each language' solution as described here - viewtopic.php?p=330#p330

The only new thing needed would be to link the EN pages with their counterpart ES pages. This can be done using relations as explained in the follow-up post to it - viewtopic.php?p=18928#p18928

Hope it helps.

Thanks for your answer, @KK. Will have a look at those posts.

But to sum it up, the folder-approach with multiple copies of the site is still the way to go?

I worked with some other systems during the last year and most of them have multi-language text fields, so you don't have to to create copies, which makes administration is a bit more convenient.

Isn't that an approach that could be implemented with CouchCMS?

[KK]

JD, unfortunately the approaches discussed at viewtopic.php?f=8&t=74 are the only ones we have for now. Maybe in the future we'll have a bonafide multi-lingual CMS.