docs: usage with NextJS article updated

[midas-png]

Background

I've faced a problem when starting developing a project using NextJS with FSD. Many time spent to get it right to combine NextJS and FSD to make it work together. There was no detailed article in the documentation of how it should work. So I decided to research the best practices of me and colleagues and describe in the article about using with NextJS

Changelog

1. Usage with NextJS article was updated in russian and english
2. sidebar_class_name: sidebar-item--wip was removed from .mdx files about usage with NextJS (in russian and english)

The WIP notification was left in the article as I think it should be updated by adding more useful links in the See also section

before:

Screenshots

 

after:

Screenshots

 

[netlify[bot]]

✅ Deploy Preview for pr-fsd ready!

Name	Link
🔨 Latest commit	c48d346689f6a3b76c0370a9eb258a4d8c627474
🔍 Latest deploy log	https://app.netlify.com/sites/pr-fsd/deploys/657f452b27d2b000084ee572
😎 Deploy Preview	https://deploy-preview-644--pr-fsd.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[illright]

Hi! This is great, I'm really glad someone actually took the time to write this up. As for the WIP status of this page, I personally think it's okay to mark this page as ready. The only thing I'd like to see are links to CodeSandbox or StackBlitz where a small version of Next is deployed along with the proposed structure, just to have something practical to look at. Could you add that please? Other than that, everything else is good

[midas-png]

Thanks! Sure, I'll take care of it

[NazariiShvets]

Thanks for your contrubition ❤️‍🔥 I believe you have done a great job 👍

I only have a problem with the `pages-flat' naming I feel that this naming has 2 problems:

1) It encourages you to structure your pages into a flat list. I would be happy if there was a mention of grouping somewhere so that users know how to structure pages if there are many of them

2) The name itself is quite ugly. Alternatives could be views or screens, but I have no experience with a nextjs project. It would be great if you could organize a poll within the community (like in the Telegram chat), collect their feedback on their choices and what names they use, and based on that response choose an appropriate name. If the community chooses pages-flat, it can be used

[midas-png]

I made a poll in the Telegram chat, but since many people use the App Router, I did not get a definite opinion on this issue. I left the option with views. Also, unfortunately, due to the high workload at work, I can't do the links to CodeSandbox now. I'm ready to deal with it later

[midas-png]

Сделал правки по комментариям. Поправил русскую и английскую версии. По главреду читаемость 9.5, в LanguageTool тоже проверил. Ссылки на route-groups удалил

[midas-png]

@illright Посмотрел, спасибо, изменения к месту