I'm wondering how we should combine manual vs Rosey translations. For example:
In UI components like navs, footer etc, Rosey translation seems perfect
For larger content sections, like product or service description (which may even be written in markdown and transformed into html) Rosey does not seem like a good fit. I would want my client to be able to add multiple languages of this from within cloudcannon.
Would it be possible to have some manual routes with the language, so mydomain.com/en/ and still be able to rely on Rosey for translating other things? Or is there maybe a completely different recommended solution?
Hi there!
I'm wondering how we should combine manual vs Rosey translations. For example:
Would it be possible to have some manual routes with the language, so mydomain.com/en/ and still be able to rely on Rosey for translating other things? Or is there maybe a completely different recommended solution?