3cf7a30df9
This PR follows #40181, adding the dark mode support for the brand new Next.js logo (BTW, the new logo is awesome!). The dark version of the logo is also served from `assets.vercel.com` (I just change the original logo URL, replace the `light` with `dark`, and surprisingly find out that doesn't result in 404). cc @Nutlope @steven-tey Ref: [Specify theme context for images in Markdown (Beta) - GitHub Blog](https://github.blog/changelog/2022-05-19-specify-theme-context-for-images-in-markdown-beta/) Currently, the Next.js README in dark mode: <img width="917" alt="image" src="https://user-images.githubusercontent.com/40715044/188449078-864f6b71-7741-44f4-aee6-02a281b0a263.png"> After the PR: <img width="914" alt="image" src="https://user-images.githubusercontent.com/40715044/188449265-a3556565-d866-4e0e-9b97-be62fba6c6fe.png"> Preview link: https://github.com/SukkaW/next.js/tree/readme-logo-darkmode
67 lines
3 KiB
Markdown
67 lines
3 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
|
|
|
|
Visit <a aria-label="next.js learn" href="https://nextjs.org/learn">https://nextjs.org/learn</a> 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 that 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
|