docs: add Tauri integration guide for Lingo.dev CLI (#1344)

[rrrr08]

#1344

Summary

This PR adds a comprehensive integration guide for using Lingo.dev CLI with Tauri desktop applications, following the same structure and quality as existing framework guides.

What's included

• Complete project setup: Step-by-step Tauri + React + TypeScript project creation
• React-intl integration: Full internationalization setup with TypeScript support
• Lingo.dev CLI configuration: Proper i18n.json setup for translation management
• Dynamic translation loading: Error handling and fallback mechanisms
• Testing instructions: Development server and production build guidance

Key features

✅ Working example: All code examples compile and run without errors
✅ TypeScript support: Proper type declarations and imports
✅ Error handling: Graceful fallbacks when translations are missing
✅ Platform support: Cross-platform instructions for Windows/macOS/Linux
✅ Best practices: Follows react-intl and Tauri conventions

Structure

The guide follows the established pattern:

1. Project Setup - Tauri installation and project creation
2. Internationalization - React-intl setup with TypeScript
3. CLI Configuration - Lingo.dev translation pipeline setup
4. Translation Process - Running the translation workflow
5. Testing - Development and production verification
6. Build Process - Production deployment preparation

Testing

• ✅ Created and tested complete Tauri project following all guide steps
• ✅ Verified TypeScript compilation without errors
• ✅ Confirmed react-intl integration works correctly
• ✅ Validated Lingo.dev CLI configuration format

The guide enables developers to build fully internationalized Tauri desktop applications with AI-powered translations managed through Lingo.dev CLI.

[davidturnbull]

Hi 👋

Thanks for the submission. I've assigned myself to review the PR in more depth and will get to it shortly.

Thanks. 😄

[github-actions[bot]]

Hey @rrrr08! Just checking in - are you still working on this PR? We noticed there are some comments that may need addressing. If you need more time, no problem! Just let us know. If we don't hear back within a week, we'll close this to keep the repo tidy, but you can always reopen when ready.