Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Combining manual and Rosey translation #43

Open
silveltman opened this issue Jun 21, 2023 · 0 comments
Open

Combining manual and Rosey translation #43

silveltman opened this issue Jun 21, 2023 · 0 comments

Comments

@silveltman
Copy link

Hi there!

I'm wondering how we should combine manual vs Rosey translations. For example:

  1. In UI components like navs, footer etc, Rosey translation seems perfect
  2. 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant