docs: create a Lingo.dev CLI integration guide for Next.js (App Router)
Context
We're building a library of integration guides that show developers how to use Lingo.dev CLI with popular frameworks and platforms. Each guide is intended to be a complete, hands-on tutorial that takes someone from zero to having a working multilingual application.
Task
Create a Lingo.dev CLI integration guide for Next.js (App Router).
The guide should:
- Follow the same general flow, scope, and structure of existing guides
- Include i18n setup instructions for a fresh Next.js project: https://nextjs.org/docs/app/guides/internationalization
- Use react-intl to render translations
Example guides
These are some examples of existing guides:
- Godot: https://lingo.dev/en/cli/frameworks/godot
- Mintlify: https://lingo.dev/en/cli/frameworks/mintlify
- Laravel: https://lingo.dev/en/cli/frameworks/laravel
- iOS: https://lingo.dev/en/cli/frameworks/ios
- React Native (Expo): https://lingo.dev/en/cli/frameworks/react-native-expo
Caveat: Merging PRs
Our documentation content lives in an internal repo. This means if you open a pull request for an integration guide, we can't merge it directly. Instead, we use the following workflow to ensure everyone receives credit for their work:
- Create a pull request for the current repo.
- In the PR, include a Markdown file that contains the integration guide (e.g.,
docs/guide.md). - We'll review the PR, working with you to get the guide into the best state possible.
- If we publish the guide on the website, we'll include a byline in the documentation that links to your GitHub profile.
- Once the documentation has been published, we'll close the PR with a comment that references the document.
Testing
Be sure to test the complete guide by carefully following all of the steps. (This is the most time-consuming part.)
Hi @davidturnbull, I have explored the existing CLI guides on Lingo.dev, and having worked with NextJS for a long time myself, I believe I can create this documentation perfectly. I also have experience with markdown language. So, it would be great if I get assigned to this issue, as I am ready to get started with it.
Hi @davidturnbull I just created a PR for this docs please review and suggest improvements or change if they are required .
Assigning this to you @KushalXCoder
@SuYaSh-PaThAk04 keep this in mind:
@sumitsaurabh927 Thanks for assigning it to me. I will update you soon with the progress.
@sumitsaurabh927 Ismy contribution Worthless?
@sumitsaurabh927 Any comments or information regarding the PR I created?