Adds a second example

[tsteckenborn]

This adds a second sample.

From my perspective the following gaps:

• When starting in dev, on client side, there's Uncaught SyntaxError: Identifier 'RefreshRuntime' has already been declared (at root.tsx:29:1). I assume some issue with the HMR due to the React Router and React Vite plugins.
• Currently the languages are hardcoded. We'd need a sample on e.g. language based on the browsers locale. Yet then the behaviour w.r.t. to the client and server entry would need to be checked (as they should return the same I assume otherwise there are hydration errors)
• I noticed that the same description and text might still result in two different translation keys. To me it's currently unclear how to best reuse translations.
• I'm currently unsure on how to best translates texts that might be included dynamically (e.g. from configuration or services)
• I'm currently unsure on how to best translate larger contents. Assuming e.g. a website would have a blog on how best return different languages or translated mdxs?

Not actually deployed yet, so we'd need to check if it works when deployed.

[kayhadrin]

Just noticing this draft PR.
For the "questions" I see in the PR description, I'd first suggest creating new discussion topics in the Q&A section. 🙂

[cpojer]

Regarding the error about RefreshRuntime, that's an issue with the React Router Vite plugin, see remix-run/react-router#12352. tl;dr: The React Router Vite plugin should be changed to take a babel option so it can be used instead of the React Vite plugin.

[tsteckenborn]

Shouldn't pnpm fbtee:translate && react-router build suffice here, as it anyways works on a different set of files then the ones created by manifest and collect?

[cpojer]

The translate command needs .source_strings.json.