[PR #988] [CLOSED] Add Next.js #44071

New Issue

2026-06-10T08:13:23-05:00

GiteaMirror commented

2026-06-10 08:13:23 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/988
Author: @ooade
Created: 6/9/2017
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (10+)

3e5937a Add Next.js
6eea305 Update readme.md
431135e Add TikZ (#966)
0199f3e Add WebExtensions
6d8b5fe Add IT Quotes (#903)
33e7089 Add description to Node.js entry (#997)
7df189e Remove Endangered Languages list (#936)
3bfdcfa Add npm scripts (#944)
ada5904 Add Python Scientific Audio (#930)
b23fafc Add Neuroscience (#962)

📊 Changes

2 files changed (+14 additions, -2 deletions)

View changed files

📝 pull_request_template.md (+1 -0)
📝 readme.md (+13 -2)

📄 Description

https://github.com/unicodeveloper/awesome-nextjs

Curated list of resources: books, videos, articles about using Next.js.

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.
For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:
- Include a short description about the list project/theme. It should not describe the list itself.
  Example: - [Fish](…) - User-friendly shell.
- Be added at the bottom of the appropriate category.
The list I'm submitting complies with these requirements:
- Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
- It's the result of hard work and the best I could possibly produce.
- Non-generated Markdown file in a GitHub repo.
- The repo should have the following GitHub topics set: awesome-list, awesome, list. I encourage you to add more relevant topics.
- Not a duplicate.
- Includes a succinct description of the project/theme at the top of the readme. (Example)
- Only has awesome items. Awesome lists are curations of the best, not everything.
- Includes a project logo/illustration whenever possible.
  - Placed at the top-right of the readme. (Example)
  - The image should link to the project website or any relevant website.
  - The image should be high-DPI. Set it to maximum half the width of the original image.
- Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
- Has the Awesome badge on the right side of the list heading,
- Has a Table of Contents section.
  - Should be named Contents, not Table of Contents.
  - Should be the first section in the list.
- Has an appropriate license.
  - That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
  - If you use a license badge, it should be SVG, not PNG.
- Has contribution guidelines.
  - The file should be named contributing.md. Casing is up to you.
- Has consistent formatting and proper spelling/grammar.
  - Each link description starts with an uppercase character and ends with a period.
    Example: - [AVA](…) - JavaScript test runner.
  - Drop all the A / An prefixes in the descriptions.
  - Consistent naming. For example, Node.js, not NodeJS or node.js.
- Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.
Go to the top and read it again.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/988 **Author:** [@ooade](https://github.com/ooade) **Created:** 6/9/2017 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (10+) - [`3e5937a`](https://github.com/sindresorhus/awesome/commit/3e5937a71a2fa17dd5ed39972187193d2bbd7edc) Add Next.js - [`6eea305`](https://github.com/sindresorhus/awesome/commit/6eea305782c31393b1e743c63a0c9ad94330e5a3) Update readme.md - [`431135e`](https://github.com/sindresorhus/awesome/commit/431135ea5ca3aa211edcf869d0fe40ae88a48bf8) Add TikZ (#966) - [`0199f3e`](https://github.com/sindresorhus/awesome/commit/0199f3e96f9733a44a53831b361fe344b754cd8f) Add WebExtensions - [`6d8b5fe`](https://github.com/sindresorhus/awesome/commit/6d8b5fe6e5c49e0dd7ebac820801fd442beb9e0a) Add IT Quotes (#903) - [`33e7089`](https://github.com/sindresorhus/awesome/commit/33e708918b05cc46197530682d200856a4a43413) Add description to Node.js entry (#997) - [`7df189e`](https://github.com/sindresorhus/awesome/commit/7df189e4adf84261f4ff6cf87d633122594ef22b) Remove Endangered Languages list (#936) - [`3bfdcfa`](https://github.com/sindresorhus/awesome/commit/3bfdcfa7068f234b50d2de6d4848935a4551aeba) Add npm scripts (#944) - [`ada5904`](https://github.com/sindresorhus/awesome/commit/ada59040ff86b89c3dfc7ed45b3275e4a2fe8100) Add Python Scientific Audio (#930) - [`b23fafc`](https://github.com/sindresorhus/awesome/commit/b23fafce0c27847585e0995317d302d3c0925890) Add Neuroscience (#962) ### 📊 Changes **2 files changed** (+14 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `pull_request_template.md` (+1 -0) 📝 `readme.md` (+13 -2) </details> ### 📄 Description   **https://github.com/unicodeveloper/awesome-nextjs** **Curated list of resources: books, videos, articles about using Next.js.** # By submitting this pull request I confirm I've read and complied with the below requirements. **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** - I have read and understood the [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) and the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md). - This pull request has a descriptive title. For example, `Add Name of List`, not `Update readme.md` or `Add awesome list`. - The entry in the Awesome list should: - Include a short description about the list project/theme. It should not describe the list itself. Example: `- [Fish](…) - User-friendly shell.` - Be added at the bottom of the appropriate category. - The list I'm submitting complies with these requirements: - **Has been around for at least 30 days.** That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. - It's the result of hard work and the best I could possibly produce. - Non-generated Markdown file in a GitHub repo. - The repo should have the following [GitHub topics](https://help.github.com/articles/about-topics) set: `awesome-list`, `awesome`, `list`. I encourage you to add more relevant topics. - Not a duplicate. - Includes a succinct description of the project/theme at the top of the readme. [(Example)](https://github.com/willempienaar/awesome-quantified-self) - Only has awesome items. Awesome lists are curations of the best, not everything. - Includes a project logo/illustration whenever possible. - Placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron) - The image should link to the project website or any relevant website. - The image should be high-DPI. Set it to maximum half the width of the original image. - Entries have a description, unless the title is descriptive enough by itself. It rarely is though. - Has the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge) on the right side of the list heading, - Has a Table of Contents section. - Should be named `Contents`, not `Table of Contents`. - Should be the first section in the list. - Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license). - That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.** - If you use a license badge, it should be SVG, not PNG. - Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines). - The file should be named `contributing.md`. Casing is up to you. - Has consistent formatting and proper spelling/grammar. - Each link description starts with an uppercase character and ends with a period. Example: `- [AVA](…) - JavaScript test runner.` - Drop all the `A` / `An` prefixes in the descriptions. - Consistent naming. For example, `Node.js`, not `NodeJS` or `node.js`. - Doesn't include a Travis badge. You can still use Travis for list linting, but the badge has no value in the readme. - Go to the top and read it again. --- 🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

GiteaMirror added the pull-request label 2026-06-10 08:13:23 -05:00

GiteaMirror closed this issue

2026-06-10 08:13:25 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#44071