zhankaam/inctagram-v2

This is a Next.js project bootstrapped with create-next-app.

Folders Structure `Feature Sliced Design`

Presentation and slides about FSD

/src - all needed functionality and components for pages

/shared - reusable functionality, detached from the specifics of the project/business.(e.g. UIKit, libs, API)
/layouts - common layouts for pages
/entities - business entities.(e.g., User, Product, Order)
/features - user interactions, actions that bring business value to the user.(e.g. SendComment, AddToCart, UsersSearch)
/widgets - compositional layer to combine entities and features into meaningful blocks.(e.g. IssuesList, UserProfile)
/pages - application pages
/templates - big parts of pages with building blocks for specific page. For the next.js pages is a file-routed directory, where one component = one route. For FSD pages, this is the flat page list layer. If you want to use both, you will have to keep two directories at once: a flat list of pages (let it be templates) and nested routes (pages). We keep the page code in templates and export it to pages. Ready.
/app - app-wide settings, styles and providers.

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.ts.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.