Unverified Commit 412dfc52 authored by Hyunseung Lee's avatar Hyunseung Lee Committed by GitHub

Update getting-started documentation (#45284)

## Documentation / Examples

- [x] Make sure the linting passes by running `pnpm build && pnpm lint`
- [x] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
Co-authored-by: 's avatarJJ Kasper <22380829+ijjk@users.noreply.github.com>
parent 9a82bba8
......@@ -79,12 +79,12 @@ These scripts refer to the different stages of developing an application:
Create two directories `pages` and `public` at the root of your application:
- `pages` - Associated with a route based on their file name. For example `pages/about.js` is mapped to `/about`
- `pages` - Associated with a route based on their file name. For example, `pages/about.js` is mapped to `/about`
- `public` - Stores static assets such as images, fonts, etc. Files inside `public` directory can then be referenced by your code starting from the base URL (`/`).
Next.js is built around the concept of [pages](/docs/basic-features/pages.md). A page is a [React Component](https://reactjs.org/docs/components-and-props.html) exported from a `.js`, `.jsx`, `.ts`, or `.tsx` file in the `pages` directory. You can even add [dynamic route](/docs/routing/dynamic-routes) parameters with the filename.
Inside the `pages` directory add the `index.js` file to get started. This is the page that is rendered when the user visits the root of your application.
Inside the `pages` directory, add the `index.js` file to get started. This is the page that is rendered when the user visits the root of your application.
Populate `pages/index.js` with the following contents:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment