Why would you use this instead of creating a related multi-lingual node with its own culture and then use the tools that Umbraco provides you for multi-lingual sites?
Depends on the project. For 1-1 multilingual sites I found this package useful for a previous project. Let's say you have a website with 20+ different languages, and every site has the exact same structure, then with vorto you wouldn't need one node for every 20 language page.
As I said, It depends on the project and what the client demands. I was very glad to find Vorto!
WHY!
Why would you use this instead of creating a related multi-lingual node with its own culture and then use the tools that Umbraco provides you for multi-lingual sites?
I don't get it?
Depends on the project. For 1-1 multilingual sites I found this package useful for a previous project. Let's say you have a website with 20+ different languages, and every site has the exact same structure, then with vorto you wouldn't need one node for every 20 language page.
As I said, It depends on the project and what the client demands. I was very glad to find Vorto!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.