awesome

Added links to 'Arabic Tools' and 'Free Developer Tools' sections. [Insert URL to the list here] [Explain what this list is about and why it should be included here] 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. Requirements for your pull request [ ] Fully AI-generated pull requests are not accepted. [ ] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility. [ ] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive. [ ] You have to review at least 4 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review. [ ] You have read and understood the instructions for creating a list. [ ] This pull request has a title in the format . It should not contain the word . ✅ ✅ ❌ ❌ ❌ ❌ ❌ ❌ [ ] Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list. ✅ ✅ ❌ ❌ ❌ [ ] Your entry should be added at the bottom of the appropriate category. [ ] The title of your entry should be title-cased and the URL to your list should end in . Example: [ ] No blockchain-related lists. [ ] The suggested Awesome list complies with the below requirements. Requirements for your Awesome list [ ] 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. [ ] Is not AI-generated. [ ] Run on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it. [ ] The default branch should be named , not . [ ] Includes a succinct description of the project/theme at the top of the readme. (Example) ✅ ✅ ❌ ❌ [ ] It's the result of hard work and the best I could possibly produce. If you have not put in considerable effort into your list, your pull request will be immediately closed. [ ] The repo name of your list should be in lowercase slug format: . ✅ ✅ ❌ ❌ [ ] The heading title of your list should be in title case format: . ✅ ✅ ❌ ❌ [ ] Non-generated Markdown file in a GitHub repo. [ ] The repo should have & as GitHub topics. I encourage you to add more relevant topics. [ ] Not a duplicate. Please search for existing submissions. [ ] Only has awesome items. Awesome lists are curations of the best, not everything. [ ] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file. [ ] Includes a project logo/illustration whenever possible. Either centered, fullwidth, or 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 a maximum of half the width of the original image. Don't include both a title saying and a logo with . You can put the header image in a (Markdown header) or `ContentsTable of ContentsContributingFootnoteshttps://github.com///community/license/new?branch=main&template=cc0-1.0licenseLICENSELicenceunicorncontributing.mdContributingFootnotes- AVA - JavaScript test runner.Node.jsNodeJSnode.jsInspired by awesome-fooInspired by the Awesome project` kinda link at the top of the readme. The Awesome badge is enough. Go to the top and read it again.

https://github.com/yudataguy/awesome-japanese A curated list of resources for learning the Japanese language — beginner guides, textbooks, courses, hiragana/katakana and kanji tools, grammar guides, reading and listening practice, dictionaries, and software, covering beginner through advanced learners. It has been open source and maintained since 2017 and fits the Learn category alongside the other learning-resource lists. By submitting this pull request I confirm I've read and complied with the below requirements 🖖 Requirements for your pull request [x] Fully AI-generated pull requests are not accepted. [x] Don't open a Draft / WIP pull request while you work on the guidelines. [x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive. [x] You have to review at least 4 other open pull requests. Reviewed: #4271 (Add Arabic Tools) #4291 (Add AgentOS) #4275 (Add Singapore CS1010) #4316 (Add NGINX) [x] You have read and understood the instructions for creating a list. [x] This pull request has a title in the format . [x] Your entry here should include a short description of the project/theme of the list. [x] Your entry should be added at the bottom of the appropriate category. [x] The title of your entry should be title-cased and the URL to your list should end in . [x] No blockchain-related lists. [x] The suggested Awesome list complies with the below requirements. Requirements for your Awesome list [x] Has been around for at least 30 days. [x] Is not AI-generated. [x] Run on your list and fix the reported issues. [x] The default branch should be named , not . [x] Includes a succinct description of the project/theme at the top of the readme. [x] It's the result of hard work and the best I could possibly produce. [x] The repo name of your list should be in lowercase slug format: . [x] The heading title of your list should be in title case format: . [x] Non-generated Markdown file in a GitHub repo. [x] The repo should have & as GitHub topics. [x] Not a duplicate. Please search for existing submissions. [x] Only has awesome items. Awesome lists are curations of the best, not everything. [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. [x] Includes a project logo/illustration whenever possible. [x] Entries have a description, unless the title is descriptive enough by itself. [x] Includes the Awesome badge. [x] Has a Table of Contents section. [x] Has an appropriate license. [x] Has contribution guidelines. [x] All non-important but necessary content is grouped in a section at the bottom of the readme. [x] Has consistent formatting and proper spelling/grammar. [x] Does not use hard-wrapping. [x] Does not include a CI badge. [x] Does not include an kinda link at the top of the readme.

https://github.com/GetPageSpeed/awesome-nginx#readme NGINX is the web server, reverse proxy and load balancer behind a large share of the web. This list covers its production ecosystem: third-party modules, distributions and forks (Angie, freenginx, OpenResty, Tengine), security/WAF tooling, packaging, and learning resources — about 200 entries, every one verified in production use. Note on the existing nginx entry in this category: that list is a general collection of articles and resources. This one is complementary, focused on the module/packaging ecosystem (which modules exist, which are maintained, how to deploy them), curated via a YAML pipeline with CI link auditing on every change, so dead or abandoned entries cannot survive a regeneration. The list is over 30 days old (first commit 2026-06-02), passes awesome-lint in CI on every push, is CC0-licensed, and has contribution guidelines. Reviewed PRs (4) — see follow-up comment. By submitting this pull request I confirm I've read and complied with the below requirements 🖖 Requirements for your pull request [ ] Fully AI-generated pull requests are not accepted. [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. [x] Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive. [x] You have to review at least 4 other open pull requests. (see follow-up comment for links) [x] You have read and understood the instructions for creating a list. [x] This pull request has a title in the format . It should not contain the word . [x] Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list. [x] Your entry should be added at the bottom of the appropriate category. [x] The title of your entry should be title-cased and the URL to your list should end in . [x] No blockchain-related lists. Requirements for your Awesome list [x] Has been around for at least 30 days. First commit: 2026-06-02. [x] Is not AI-generated. [x] Run on your list and fix the reported issues. Passing in CI on every push. [x] The default branch should be named . [x] Includes a succinct description of the project/theme at the top of the readme.** [x] It's the result of hard work and the best I could possibly produce. 200+ entries, every one verified in production use, curated over years of NGINX packaging work. [x] The repo name of your list should be in lowercase slug format: . [x] The heading title of your list should be in title case format: . [x] Non-generated Markdown file in a GitHub repo. [x] The repo should have & as GitHub topics. [x] Not a duplicate. The existing list is a different scope (articles/resources); this list covers the module/packaging ecosystem. [x] Only has awesome items. Awesome lists are curations of the best, not everything. [x] Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. CI link auditing ensures this on every push. [x] Includes a project logo/illustration. [x] Entries have a description. [x] Includes the Awesome badge. [x] Has a Table of Contents section named . [x] Has an appropriate license. CC0. [x] Has contribution guidelines (). [x] Has consistent formatting and proper spelling/grammar. [x] Does not use hard-wrapping. [x] Does not include a CI badge. [x] Does not include an "Inspired by awesome-foo" link.