Skip to content

Commit 4db1ae9

Browse files
docs: update file structure (#71951)
## Summary Sync [`04-functions`](https://github.com/vercel/next.js/tree/canary/docs/02-app/02-api-reference/04-functions) and [`01-routing`](https://github.com/vercel/next.js/tree/canary/docs/02-app/01-building-your-application/01-routing) file convention. ### Improving Documentation - [x] Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - [x] Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide Co-authored-by: Delba de Oliveira <[email protected]>
1 parent 6ae6605 commit 4db1ae9

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/05-community/01-contribution-guide.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -72,20 +72,20 @@ The file structure reflects the navigation that you see on the site, and by defa
7272
For example, in the [functions API Reference](/docs/app/api-reference/functions), the pages are sorted alphabetically because it makes it easier for developers to find a specific function:
7373

7474
```txt
75-
03-functions
75+
04-functions
76+
├── cacheTag.mdx
77+
├── connection.mdx
7678
├── cookies.mdx
77-
├── draft-mode.mdx
78-
├── fetch.mdx
7979
└── ...
8080
```
8181

8282
But, in the [routing section](/docs/app/building-your-application/routing), the files are prefixed with a two-digit number, sorted in the order developers should learn these concepts:
8383

8484
```txt
85-
02-routing
85+
01-routing
8686
├── 01-defining-routes.mdx
87-
├── 02-pages-and-layouts.mdx
88-
├── 03-linking-and-navigating.mdx
87+
├── 02-pages.mdx
88+
├── 03-layouts-and-templates.mdx
8989
└── ...
9090
```
9191

0 commit comments

Comments
 (0)