Next.js

## Getting Started Visit https://nextjs.org/learn to get started with Next.js. ## Documentation Visit [https://nextjs.org/docs](https://nextjs.org/docs) to view the full documentation. ## Who is using Next.js? Next.js is used by the world's leading companies. Check out the [Next.js Showcase](https://nextjs.org/showcase) to learn more. ## Community The Next.js community can be found on [GitHub Discussions](https://github.com/vercel/next.js/discussions), where you can ask questions, voice ideas, and share your projects. To chat with other community members you can join the [Next.js Discord](https://nextjs.org/discord). Our [Code of Conduct](https://github.com/vercel/next.js/blob/canary/CODE_OF_CONDUCT.md) applies to all Next.js community channels. ## Contributing Please see our [contributing.md](/contributing.md). ### Good First Issues We have a list of [good first issues](https://github.com/vercel/next.js/labels/good%20first%20issue) that contain bugs which have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process. ## Authors - Tim Neutkens ([@timneutkens](https://twitter.com/timneutkens)) - Naoyuki Kanezawa ([@nkzawa](https://twitter.com/nkzawa)) - Guillermo Rauch ([@rauchg](https://twitter.com/rauchg)) - Arunoda Susiripala ([@arunoda](https://twitter.com/arunoda)) - Tony Kovanen ([@tonykovanen](https://twitter.com/tonykovanen)) - Dan Zajdband ([@impronunciable](https://twitter.com/impronunciable)) ## Security If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and not open a public issue. We will investigate all legitimate reports. Email `security@vercel.com` to disclose any security vulnerabilities. https://vercel.com/security