a7faeb0b80
## Description This Pull Request improves the visual appearance of the badges in the README.md file by removing unnecessary line breaks between the badge images, eliminating the unwanted blue link lines that previously appeared and resulting in a cleaner and more cohesive look. ### What Removed unnecessary line breaks between badge images in the README.md file to eliminate the unwanted blue link lines and improve the overall visual presentation. ### Why Previously, the badges were displayed with line breaks between them, causing blue link lines to appear, which disrupted the clean look of the badges. By removing these line breaks, the badges now appear without the blue link lines, providing a more cohesive and visually appealing README. ### How - Removed the line breaks between badge images in the README.md file. Co-authored-by: Jiwon Choi <devjiwonchoi@gmail.com>
60 lines
3.7 KiB
Markdown
60 lines
3.7 KiB
Markdown
<p align="center">
|
|
<a href="https://nextjs.org">
|
|
<picture>
|
|
<source media="(prefers-color-scheme: dark)" srcset="https://assets.vercel.com/image/upload/v1662130559/nextjs/Icon_dark_background.png">
|
|
<img src="https://assets.vercel.com/image/upload/v1662130559/nextjs/Icon_light_background.png" height="128">
|
|
</picture>
|
|
<h1 align="center">Next.js</h1>
|
|
</a>
|
|
</p>
|
|
|
|
<p align="center">
|
|
<a aria-label="Vercel logo" href="https://vercel.com"><img src="https://img.shields.io/badge/MADE%20BY%20Vercel-000000.svg?style=for-the-badge&logo=Vercel&labelColor=000"></a>
|
|
<a aria-label="NPM version" href="https://www.npmjs.com/package/next"><img alt="" src="https://img.shields.io/npm/v/next.svg?style=for-the-badge&labelColor=000000"></a>
|
|
<a aria-label="License" href="https://github.com/vercel/next.js/blob/canary/license.md"><img alt="" src="https://img.shields.io/npm/l/next.svg?style=for-the-badge&labelColor=000000"></a>
|
|
<a aria-label="Join the community on GitHub" href="https://github.com/vercel/next.js/discussions"><img alt="" src="https://img.shields.io/badge/Join%20the%20community-blueviolet.svg?style=for-the-badge&logo=Next.js&labelColor=000000&logoWidth=20"></a>
|
|
</p>
|
|
|
|
## Getting Started
|
|
|
|
Used by some of the world's largest companies, Next.js enables you to create full-stack web applications by extending the latest React features, and integrating powerful Rust-based JavaScript tooling for the fastest builds.
|
|
|
|
- Visit our [Learn Next.js](https://nextjs.org/learn) course to get started with Next.js.
|
|
- Visit the [Next.js Showcase](https://nextjs.org/showcase) to see more sites built with Next.js.
|
|
|
|
## Documentation
|
|
|
|
Visit [https://nextjs.org/docs](https://nextjs.org/docs) to view the full documentation.
|
|
|
|
## 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 with other people.
|
|
|
|
To chat with other community members you can join the Next.js [Discord](https://nextjs.org/discord) server.
|
|
|
|
Do note that our [Code of Conduct](https://github.com/vercel/next.js/blob/canary/CODE_OF_CONDUCT.md) applies to all Next.js community channels. Users are **highly encouraged** to read and adhere to them to avoid repercussions.
|
|
|
|
## Contributing
|
|
|
|
Contributions to Next.js are welcome and highly appreciated. However, before you jump right into it, we would like you to review our [Contribution Guidelines](/contributing.md) to make sure you have a smooth experience contributing to Next.js.
|
|
|
|
### Good First Issues:
|
|
|
|
We have a list of **[good first issues](https://github.com/vercel/next.js/labels/good%20first%20issue)** that contain bugs that have a relatively limited scope. This is a great place for newcomers and beginners alike to get started, gain experience, and get familiar with our contribution process.
|
|
|
|
## Authors
|
|
|
|
A list of the original co-authors of Next.js that helped bring this amazing framework to life!
|
|
|
|
- Tim Neutkens ([@timneutkens](https://x.com/timneutkens))
|
|
- Naoyuki Kanezawa ([@nkzawa](https://x.com/nkzawa))
|
|
- Guillermo Rauch ([@rauchg](https://x.com/rauchg))
|
|
- Arunoda Susiripala ([@arunoda](https://x.com/arunoda))
|
|
- Tony Kovanen ([@tonykovanen](https://x.com/tonykovanen))
|
|
- Dan Zajdband ([@impronunciable](https://x.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. Alternatively, you can visit this [link](https://vercel.com/security) to know more about Vercel's security and report any security vulnerabilities.
|