moves sample for next.js to its repo so we do not have to sync those …

…anylonger

example/nextjs/README.md

@@ -1,51 +1,13 @@
 # Getting started
 
-Build with [next.js](https://github.com/zeit/next.js/).
+You find the example for next.js and react-i18next here:
 
-```bash
-# npm install
-# npm run dev
-```
+[https://github.com/zeit/next.js/tree/canary/examples/with-react-i18next](https://github.com/zeit/next.js/tree/canary/examples/with-react-i18next)
 
-**open:**
+*Using one place for the example makes it easier so we do not have to sync them on every change.*
 
-auto detecting user language: [http://localhost:3000](http://localhost:3000)
+Beside that there is also a sample to show the usage with **locize** here:
 
-german: [http://localhost:3000/?lng=de](http://localhost:3000/?lng=de)
+[https://github.com/i18next/react-i18next/tree/master/example/nextjs-locize](https://github.com/i18next/react-i18next/tree/master/example/nextjs-locize)
 
-english: [http://localhost:3000/?lng=en](http://localhost:3000/?lng=en)
-
-
-## The idea behind the example
-
-This example app shows how to integrate [react-i18next](https://github.com/i18next/react-i18next) with [Next](https://github.com/zeit/next.js).
-
-**Plus:**
-
-- Routing and separating translations into multiple files (lazy load them on client routing)
-- Child components (pure or using translation hoc)
-
-### Features of this example app
-
-- Server-side language negotiation
-- Full control and usage of i18next on express server using [i18next-express-middleware](https://github.com/i18next/i18next-express-middleware) which asserts no async request collisions resulting in wrong language renderings
-- Support for save missing features to get untranslated keys automatically created `locales/{lng}/{namespace}.missing.json` -> never miss to translate a key
-- Proper pass down on translations via initialProps
-- Taking advantage of multiple translation files including lazy loading on client (no need to load all translations upfront)
-- Use express to also serve translations for clientside
-- In contrast to react-intl the translations are visible both during development and in production
-
-### learn more
-
-- [next.js](https://github.com/zeit/next.js)
-- [react-i18next repository](https://github.com/i18next/react-i18next)
-- [react-i18next documentation](https://react.i18next.com)
-
-**Translation features:**
-
-- [i18next repository](https://github.com/i18next/i18next)
-- [i18next documentation](https://www.i18next.com)
-
-**Translation management:**
-
-- [locize](http://locize.com)
+If you like to cover the full localization process beside instrumenting your code for i18n.