[PR #947] [CLOSED] Add Awesome Hexo #1179

New Issue

GiteaMirror · 2025-11-06T15:34:26-06:00

GiteaMirror commented

2025-11-06 15:34:26 -06:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/947
Author: @NoahDragon
Created: 4/27/2017
Status: ❌ Closed

Base: master ← Head: patch-1

📝 Commits (1)

19f9aeb Update readme.md

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

Awesome Hexo

The awesome-hexo list is about the Hexo, a fast, simple & powerful blog framework, and its ecosystem. The Hexo is building upon Node.js, and help user to build simple and elegant static website. This list could provide users the resources like tutorial, API, themes, plugins, and so on. Although the list is quite young, Hexo has created since 2012, there will be many resources waiting to be added to it.

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/947 **Author:** [@NoahDragon](https://github.com/NoahDragon) **Created:** 4/27/2017 **Status:** ❌ Closed **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`19f9aeb`](https://github.com/sindresorhus/awesome/commit/19f9aebc47111b543446458ea93ff7afebb0ef23) Update readme.md ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description   **[Awesome Hexo](https://github.com/hexojs/awesome-hexo)** **The awesome-hexo list is about the Hexo, a fast, simple & powerful blog framework, and its ecosystem. The Hexo is building upon Node.js, and help user to build simple and elegant static website. This list could provide users the resources like tutorial, API, themes, plugins, and so on. Although the list is quite young, Hexo has created since 2012, there will be many resources waiting to be added to it.** # 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 2025-11-06 15:34:26 -06:00

GiteaMirror closed this issue

2025-11-06 15:34:26 -06:00

GiteaMirror referenced this issue

2025-11-06 15:39:01 -06:00

[PR #1179] [CLOSED] Add awesome-django-rest-framework list #1375

GiteaMirror referenced this issue

2026-04-15 11:29:43 -05:00

[PR #1179] [CLOSED] Add awesome-django-rest-framework list #3980

GiteaMirror referenced this issue

2026-04-17 11:41:35 -05:00

[PR #1179] [CLOSED] Add awesome-django-rest-framework list #6740