-
Notifications
You must be signed in to change notification settings - Fork 206
docs: usage with NextJS article updated #644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: usage with NextJS article updated #644
Conversation
✅ Deploy Preview for pr-fsd ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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 |
Thanks! Sure, I'll take care of it |
Thanks for your contrubition ❤️🔥 I believe you have done a great job 👍 I only have a problem with the `pages-flat' naming
|
empty links to codesandbox added
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Не переживай насчет примеров, если загружен по работе — добавить всегда успеем, это не блокер для этого ПРа. Вчитался сейчас в текст, оставил несколько комментариев и предложений. Еще было бы клево пройтись по тексту через Главред (русский) и LanguageTool (английский), чтоб местами улучшить читаемость и отловить грамматические ошибки, если они имеются
i18n/ru/docusaurus-plugin-content-docs/current/guides/tech/with-nextjs.mdx
Outdated
Show resolved
Hide resolved
i18n/ru/docusaurus-plugin-content-docs/current/guides/tech/with-nextjs.mdx
Outdated
Show resolved
Hide resolved
i18n/ru/docusaurus-plugin-content-docs/current/guides/tech/with-nextjs.mdx
Outdated
Show resolved
Hide resolved
i18n/ru/docusaurus-plugin-content-docs/current/guides/tech/with-nextjs.mdx
Outdated
Show resolved
Hide resolved
i18n/ru/docusaurus-plugin-content-docs/current/guides/tech/with-nextjs.mdx
Outdated
Show resolved
Hide resolved
i18n/ru/docusaurus-plugin-content-docs/current/guides/tech/with-nextjs.mdx
Outdated
Show resolved
Hide resolved
i18n/ru/docusaurus-plugin-content-docs/current/guides/tech/with-nextjs.mdx
Outdated
Show resolved
Hide resolved
group routes links deleted
Сделал правки по комментариям. Поправил русскую и английскую версии. По главреду читаемость 9.5, в LanguageTool тоже проверил. Ссылки на route-groups удалил |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@midas-png Я добавил небольшой моментик про проектные знания. Также я изменил путь импорта в одном месте и убрал остаточные пробелы. Посмотри, пожалуйста, скажи, что думаешь насчет этих изменений. С моей стороны никаких больше комментариев, можем вливать.
@illright Посмотрел, спасибо, изменения к месту |
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
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