diff --git a/.github/ISSUE_TEMPLATE/category-proposal.yml b/.github/ISSUE_TEMPLATE/category-proposal.yml
new file mode 100644
index 0000000..601cdfb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/category-proposal.yml
@@ -0,0 +1,34 @@
+name: Category proposal
+description: Suggest a new category or reorganization.
+title: "[Category Proposal]: "
+labels:
+  - type:taxonomy
+  - area:categories
+  - status:triage
+body:
+  - type: dropdown
+    id: proposal-type
+    attributes:
+      label: Proposal type
+      options:
+        - Add category
+        - Merge categories
+        - Rename category
+        - Split category
+    validations:
+      required: true
+
+  - type: textarea
+    id: current-state
+    attributes:
+      label: Current state
+      description: Explain the current structure and problem.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposed-change
+    attributes:
+      label: Proposed change
+    validations:
+      required: true
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 0000000..ba76823
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security policy
+    url: https://github.com/dailydotdev/awesome-developer-essentials/security/policy
+    about: Please report security issues privately when possible.
+  - name: Code of conduct
+    url: https://github.com/dailydotdev/awesome-developer-essentials/blob/main/code-of-conduct.md
+    about: Please review community expectations before posting.
diff --git a/.github/ISSUE_TEMPLATE/report-dead-link.yml b/.github/ISSUE_TEMPLATE/report-dead-link.yml
new file mode 100644
index 0000000..6327c4a
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/report-dead-link.yml
@@ -0,0 +1,37 @@
+name: Report dead link
+description: Report a broken or redirected resource URL.
+title: "[Dead Link]: "
+labels:
+  - type:bug
+  - area:links
+  - priority:high
+  - status:triage
+body:
+  - type: input
+    id: section
+    attributes:
+      label: Section
+      description: Category where the broken link appears.
+    validations:
+      required: true
+
+  - type: input
+    id: resource-name
+    attributes:
+      label: Resource name
+    validations:
+      required: true
+
+  - type: input
+    id: broken-url
+    attributes:
+      label: Broken URL
+      placeholder: https://example.com
+    validations:
+      required: true
+
+  - type: input
+    id: replacement-url
+    attributes:
+      label: Suggested replacement URL
+      placeholder: https://example.com
diff --git a/.github/ISSUE_TEMPLATE/suggest-a-resource.yml b/.github/ISSUE_TEMPLATE/suggest-a-resource.yml
new file mode 100644
index 0000000..d4d1a27
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/suggest-a-resource.yml
@@ -0,0 +1,41 @@
+name: Suggest a resource
+description: Propose a new resource for the awesome list.
+title: "[Suggestion]: "
+labels:
+  - type:suggestion
+  - area:content
+  - status:triage
+body:
+  - type: input
+    id: resource-name
+    attributes:
+      label: Resource name
+      description: Name of the resource you want to add.
+    validations:
+      required: true
+
+  - type: input
+    id: resource-url
+    attributes:
+      label: Canonical URL
+      description: Direct homepage URL.
+      placeholder: https://example.com
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Suggested list description
+      description: Use list format: [Name](URL) - Description.
+      placeholder: "[Example](https://example.com) - One-sentence factual description."
+    validations:
+      required: true
+
+  - type: textarea
+    id: why
+    attributes:
+      label: Why this belongs
+      description: Explain scope fit and uniqueness.
+    validations:
+      required: true
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..570de37
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,26 @@
+## Description
+
+Describe what changed and why it should be included.
+
+## Type of change
+
+- [ ] Add a new resource
+- [ ] Update an existing resource
+- [ ] Fix formatting/typos
+- [ ] Improve categorization
+
+## Checklist
+
+- [ ] I have read `contributing.md`.
+- [ ] My change is specifically relevant to developer essentials.
+- [ ] I used the format `[Name](URL) - Description.` for list entries.
+- [ ] I checked for duplicate entries.
+- [ ] Descriptions are concise, objective, and end with a period.
+- [ ] I verified links are valid and not broken.
+- [ ] I used canonical HTTPS URLs without shorteners or tracking parameters.
+- [ ] I disclosed any affiliation with the added/updated resource.
+- [ ] This pull request contains a single logical change.
+
+## Additional context
+
+Add references or screenshots if they help review.
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
new file mode 100644
index 0000000..e4a6704
--- /dev/null
+++ b/.github/dependabot.yml
@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: chore
diff --git a/.github/labels.yml b/.github/labels.yml
new file mode 100644
index 0000000..3563883
--- /dev/null
+++ b/.github/labels.yml
@@ -0,0 +1,42 @@
+- name: type:suggestion
+  color: "0E8A16"
+  description: New resource suggestions.
+- name: type:bug
+  color: "D73A4A"
+  description: Broken links, factual errors, or regressions.
+- name: type:taxonomy
+  color: "1D76DB"
+  description: Category structure changes.
+- name: type:maintenance
+  color: "6F42C1"
+  description: Recurring upkeep work.
+
+- name: area:links
+  color: "5319E7"
+  description: URL and link-quality tasks.
+- name: area:categories
+  color: "0E8A16"
+  description: Category naming and placement tasks.
+- name: area:content
+  color: "FBCA04"
+  description: Description and editorial tasks.
+
+- name: status:triage
+  color: "BFD4F2"
+  description: Needs maintainer review.
+- name: status:needs-info
+  color: "D4C5F9"
+  description: Missing required details.
+- name: status:ready
+  color: "0E8A16"
+  description: Ready for implementation.
+
+- name: priority:high
+  color: "B60205"
+  description: Time-sensitive quality work.
+- name: priority:medium
+  color: "FBCA04"
+  description: Important improvements.
+- name: priority:low
+  color: "C2E0C6"
+  description: Nice-to-have tasks.
diff --git a/.github/workflows/lint.yml b/.github/workflows/lint.yml
new file mode 100644
index 0000000..22b5647
--- /dev/null
+++ b/.github/workflows/lint.yml
@@ -0,0 +1,39 @@
+name: Lint
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+jobs:
+  guard-internal-files:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v6
+
+      - name: Block internal planning files
+        run: |
+          if [ -f "PLAN.md" ] || [ -f "PROMOTION.md" ]; then
+            echo "Internal planning files must not be committed."
+            echo "Remove PLAN.md and PROMOTION.md from git."
+            exit 1
+          fi
+
+  awesome-lint:
+    needs: guard-internal-files
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version: 20
+
+      - name: Run awesome-lint
+        run: npx awesome-lint
diff --git a/.github/workflows/maintenance.yml b/.github/workflows/maintenance.yml
new file mode 100644
index 0000000..134b8fb
--- /dev/null
+++ b/.github/workflows/maintenance.yml
@@ -0,0 +1,117 @@
+name: Maintenance
+
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: "0 9 * * 1"
+    - cron: "0 9 1 * *"
+
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+  link-check:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v6
+
+      - name: Run link checker
+        id: lychee
+        continue-on-error: true
+        run: |
+          npx lychee \
+            --verbose \
+            --no-progress \
+            --max-concurrency 8 \
+            --accept 200,429 \
+            --format markdown \
+            README.md > lychee-report.md
+
+      - name: Count dead links
+        id: dead-links
+        run: |
+          if [ "${{ steps.lychee.outcome }}" = "success" ]; then
+            echo "dead_count=0" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+          dead_count=$(awk '/^\s*\[✗\]/{count++} END {print count+0}' lychee-report.md)
+          echo "dead_count=${dead_count:-0}" >> "$GITHUB_OUTPUT"
+
+      - name: Open or update dead-link issue
+        if: steps.dead-links.outputs.dead_count != '0'
+        uses: actions/github-script@v8
+        with:
+          script: |
+            const fs = require("fs");
+            const title = "Automated dead link report";
+            const report = fs.readFileSync("lychee-report.md", "utf8");
+            const body = [
+              "## Dead links detected",
+              "",
+              `Detected by scheduled maintenance run on ${new Date().toISOString()}.`,
+              "",
+              `Dead links found: ${process.env.DEAD_COUNT}`,
+              "",
+              "### Report",
+              "",
+              report
+            ].join("\n");
+
+            const { data: issues } = await github.rest.issues.listForRepo({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              state: "open"
+            });
+
+            const existing = issues.find((issue) => issue.title === title);
+
+            if (existing) {
+              await github.rest.issues.update({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: existing.number,
+                body
+              });
+            } else {
+              await github.rest.issues.create({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                title,
+                body,
+                labels: ["type:maintenance", "area:links", "priority:high"]
+              });
+            }
+        env:
+          DEAD_COUNT: ${{ steps.dead-links.outputs.dead_count }}
+
+  monthly-stale-entry-review:
+    if: github.event_name == 'workflow_dispatch' || (github.event_name == 'schedule' && github.event.schedule == '0 9 1 * *')
+    runs-on: ubuntu-latest
+    steps:
+      - name: Open monthly stale-entry review issue
+        uses: actions/github-script@v8
+        with:
+          script: |
+            const now = new Date().toISOString().slice(0, 10);
+            const title = `Monthly stale entry review (${now.slice(0, 7)})`;
+            const body = [
+              "## Monthly stale entry review",
+              "",
+              "Review the list for stale entries and open targeted cleanup PRs.",
+              "",
+              "### Checklist",
+              "- [ ] Verify links for recently changed websites.",
+              "- [ ] Remove or replace deprecated entries.",
+              "- [ ] Refresh outdated descriptions.",
+              "- [ ] Re-check category fit for recent additions."
+            ].join("\\n");
+
+            await github.rest.issues.create({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              title,
+              body,
+              labels: ["type:maintenance", "priority:medium", "status:triage"]
+            });
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..ff81a8c
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,2 @@
+PLAN.md
+PROMOTION.md
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..cd36804
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,116 @@
+CC0 1.0 Universal
+
+Statement of Purpose
+
+The laws of most jurisdictions throughout the world automatically confer
+exclusive Copyright and Related Rights (defined below) upon the creator and
+subsequent owner(s) (each and all, an "owner") of an original work of
+authorship and/or a database (each, a "Work").
+
+Certain owners wish to permanently relinquish those rights to a Work for the
+purpose of contributing to a commons of creative, cultural and scientific
+works ("Commons") that the public can reliably and without fear of later
+claims of infringement build upon, modify, incorporate in other works, reuse
+and redistribute as freely as possible in any form whatsoever and for any
+purposes, including without limitation commercial purposes. These owners may
+contribute to the Commons to promote the ideal of a free culture and the
+further production of creative, cultural and scientific works, or to gain
+reputation or greater distribution for their Work in part through the use and
+efforts of others.
+
+For these and/or other purposes and motivations, and without any expectation
+of additional consideration or compensation, the person associating CC0 with a
+Work (the "Affirmer"), to the extent that he or she is an owner of Copyright
+and Related Rights in the Work, voluntarily elects to apply CC0 to the Work
+and publicly distribute the Work under its terms, with knowledge of his or her
+Copyright and Related Rights in the Work and the meaning and intended legal
+effect of CC0 on those rights.
+
+1. Copyright and Related Rights. A Work made available under CC0 may be
+protected by copyright and related or neighboring rights ("Copyright and
+Related Rights"). Copyright and Related Rights include, but are not limited
+to, the following:
+
+  i. the right to reproduce, adapt, distribute, perform, display, communicate,
+  and translate a Work;
+
+  ii. moral rights retained by the original author(s) and/or performer(s);
+
+  iii. publicity and privacy rights pertaining to a person's image or likeness
+  depicted in a Work;
+
+  iv. rights protecting against unfair competition in regards to a Work,
+  subject to the limitations in paragraph 4(a), below;
+
+  v. rights protecting the extraction, dissemination, use and reuse of data in
+  a Work;
+
+  vi. database rights (such as those arising under Directive 96/9/EC of the
+  European Parliament and of the Council of 11 March 1996 on the legal
+  protection of databases, and under any national implementation thereof,
+  including any amended or successor version of such directive); and
+
+  vii. other similar, equivalent or corresponding rights throughout the world
+  based on applicable law or treaty, and any national implementations thereof.
+
+2. Waiver. To the greatest extent permitted by, but not in contravention of,
+applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and
+unconditionally waives, abandons, and surrenders all of Affirmer's Copyright
+and Related Rights and associated claims and causes of action, whether now
+known or unknown (including existing as well as future claims and causes of
+action), in the Work (i) in all territories worldwide, (ii) for the maximum
+duration provided by applicable law or treaty (including future time
+extensions), (iii) in any current or future medium and for any number of
+copies, and (iv) for any purpose whatsoever, including without limitation
+commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes
+the Waiver for the benefit of each member of the public at large and to the
+detriment of Affirmer's heirs and successors, fully intending that such Waiver
+shall not be subject to revocation, rescission, cancellation, termination, or
+any other legal or equitable action to disrupt the quiet enjoyment of the Work
+by the public as contemplated by Affirmer's express Statement of Purpose.
+
+3. Public License Fallback. Should any part of the Waiver for any reason be
+judged legally invalid or ineffective under applicable law, then the Waiver
+shall be preserved to the maximum extent permitted taking into account
+Affirmer's express Statement of Purpose. In addition, to the extent the Waiver
+is so judged Affirmer hereby grants to each affected person a royalty-free,
+non transferable, non sublicensable, non exclusive, irrevocable and
+unconditional license to exercise Affirmer's Copyright and Related Rights in
+the Work (i) in all territories worldwide, (ii) for the maximum duration
+provided by applicable law or treaty (including future time extensions), (iii)
+in any current or future medium and for any number of copies, and (iv) for any
+purpose whatsoever, including without limitation commercial, advertising or
+promotional purposes (the "License"). The License shall be deemed effective as
+of the date CC0 was applied by Affirmer to the Work. Should any part of the
+License for any reason be judged legally invalid or ineffective under
+applicable law, such partial invalidity or ineffectiveness shall not invalidate
+the remainder of the License, and in such case Affirmer hereby affirms that he
+or she will not (i) exercise any of his or her remaining Copyright and Related
+Rights in the Work or (ii) assert any associated claims and causes of action
+with respect to the Work, in either case contrary to Affirmer's express
+Statement of Purpose.
+
+4. Limitations and Disclaimers.
+
+  a. No trademark or patent rights held by Affirmer are waived, abandoned,
+  surrendered, licensed or otherwise affected by this document.
+
+  b. Affirmer offers the Work as-is and makes no representations or warranties
+  of any kind concerning the Work, express, important, statutory or otherwise,
+  including without limitation warranties of title, merchantability, fitness
+  for a particular purpose, non infringement, or the absence of latent or
+  other defects, accuracy, or the present or absence of errors, whether or not
+  discoverable, all to the greatest extent permissible under applicable law.
+
+  c. Affirmer disclaims responsibility for clearing rights of other persons
+  that may apply to the Work or any use thereof, including without limitation
+  any person's Copyright and Related Rights in the Work. Further, Affirmer
+  disclaims responsibility for obtaining any necessary consents, permissions or
+  other rights required for any use of the Work.
+
+  d. Affirmer understands and acknowledges that Creative Commons is not a
+  party to this document and has no duty or obligation with respect to this CC0
+  or use of the Work.
+
+For more information, please see
+<http://creativecommons.org/publicdomain/zero/1.0/>
diff --git a/README.md b/README.md
new file mode 100644
index 0000000..79ceaed
--- /dev/null
+++ b/README.md
@@ -0,0 +1,279 @@
+# Awesome Developer Essentials [![Awesome](https://awesome.re/badge-flat2.svg)](https://awesome.re)
+
+> Staying informed, productive, and growing as a software developer.
+
+Developers stay updated by reading blogs, scanning communities, and hearing about tools from people they trust. This list curates practical places to follow developer news, discover new frameworks, join technical communities, improve daily workflow, and build long-term career depth.
+
+## Contents
+
+- [News Aggregators and Feeds](#news-aggregators-and-feeds)
+- [Newsletters](#newsletters)
+- [Individual Developer Blogs](#individual-developer-blogs)
+- [Company Engineering Blogs](#company-engineering-blogs)
+- [Podcasts and YouTube Channels](#podcasts-and-youtube-channels)
+- [Developer Surveys and Trend Reports](#developer-surveys-and-trend-reports)
+- [Developer Communities and Forums](#developer-communities-and-forums)
+- [Developer Social Networks](#developer-social-networks)
+- [Browser Extensions](#browser-extensions)
+- [Code Editors and IDEs](#code-editors-and-ides)
+- [AI Coding Assistants](#ai-coding-assistants)
+- [Productivity and Workflow Tools](#productivity-and-workflow-tools)
+- [Tool Discovery Platforms](#tool-discovery-platforms)
+- [Job Boards and Career Platforms](#job-boards-and-career-platforms)
+- [Developer Profile and Portfolio](#developer-profile-and-portfolio)
+- [Learning Platforms](#learning-platforms)
+- [Coding Practice and Challenges](#coding-practice-and-challenges)
+- [Books](#books)
+- [See Also](#see-also)
+- [Last Verified](#last-verified)
+
+## News Aggregators and Feeds
+
+*Platforms that aggregate developer news so you can stay updated without checking dozens of sites.*
+
+- [daily.dev](https://daily.dev) - Personalized developer news feed that ranks stories by your interests.
+- [Hacker News](https://news.ycombinator.com) - Link and discussion forum focused on software, startups, and computing.
+- [Lobsters](https://lobste.rs) - Community-curated discussion feed focused on computing topics.
+- [DevURLs](https://devurls.com) - Curated stream of developer links sourced from technical publications.
+- [Echo JS](https://echojs.com) - JavaScript-focused news stream with community voting.
+- [Techmeme](https://www.techmeme.com) - Aggregated technology headlines from multiple publications.
+- [Hckr News](https://hckrnews.com) - Alternative interface for browsing Hacker News stories and threads.
+- [Refind](https://refind.com) - Personalized knowledge feed that recommends technical articles by reading patterns.
+
+## Newsletters
+
+*Newsletters that deliver programming news, tool releases, and engineering insights to your inbox.*
+
+- [TLDR](https://tldr.tech) - Daily digest of software, startup, and engineering updates.
+- [JavaScript Weekly](https://javascriptweekly.com) - Weekly roundup covering JavaScript ecosystem changes.
+- [Frontend Focus](https://frontendfoc.us) - Weekly frontend newsletter covering CSS, JavaScript, and tooling.
+- [Bytes](https://bytes.dev) - JavaScript-focused newsletter with practical links and commentary.
+- [Changelog News](https://changelog.com/news) - Weekly open source and developer tooling highlights.
+- [Python Weekly](https://www.pythonweekly.com) - Weekly collection of Python articles and releases.
+- [Golang Weekly](https://golangweekly.com) - Weekly digest of Go ecosystem updates and resources.
+- [Quastor](https://www.quastor.org) - Engineering newsletter focused on backend and system design content.
+
+## Individual Developer Blogs
+
+*Blogs by engineers worth following for deep technical insight.*
+
+- [Martin Fowler](https://martinfowler.com) - Essays on software architecture, refactoring, and engineering practices.
+- [Julia Evans](https://jvns.ca) - Practical articles that explain systems and debugging topics.
+- [Dan Luu](https://danluu.com) - Long-form writing on engineering decisions and software trade-offs.
+- [Josh W. Comeau](https://www.joshwcomeau.com) - Frontend-focused tutorials and deep dives on web platform behavior.
+- [Simon Willison's Weblog](https://simonwillison.net) - Notes on developer tooling, data workflows, and AI-assisted coding.
+- [Overreacted](https://overreacted.io) - Articles on React, JavaScript, and software thinking patterns.
+- [Coding Horror](https://blog.codinghorror.com) - Commentary on software development culture and product building.
+- [Troy Hunt](https://www.troyhunt.com) - Security-focused writing for developers and technology teams.
+
+## Company Engineering Blogs
+
+*Technical blogs from engineering teams sharing how they build and scale systems.*
+
+- [Airbnb Engineering & Data Science](https://airbnb.tech) - Engineering articles on infrastructure, data, and product systems.
+- [Stripe Engineering](https://stripe.com/blog/engineering) - Architecture and product infrastructure posts from payment systems teams.
+- [Cloudflare Blog](https://blog.cloudflare.com) - Deep dives into networking, performance, and web platform security.
+- [GitHub Blog Engineering](https://github.blog/category/engineering) - Articles about platform architecture and developer workflows.
+- [Shopify Engineering](https://shopify.engineering) - Lessons from building and operating commerce infrastructure.
+- [Slack Engineering](https://slack.engineering) - Writing on distributed systems and internal developer tooling.
+- [Datadog Engineering](https://www.datadoghq.com/blog/engineering) - Monitoring and platform engineering case studies.
+- [LinkedIn Engineering](https://engineering.linkedin.com) - Engineering posts on scaling systems and platform development.
+
+## Podcasts and YouTube Channels
+
+*Audio and video content for keeping up with developer tools and frameworks.*
+
+- [Syntax](https://syntax.fm) - Web development podcast with practical tooling episodes.
+- [Software Engineering Daily](https://softwareengineeringdaily.com) - Interview podcast covering engineering systems and organizations.
+- [The Changelog Podcast](https://changelog.com/podcast) - Conversations with open source maintainers and builders.
+- [JS Party](https://changelog.com/jsparty) - Panel podcast focused on JavaScript ecosystem developments.
+- [Fireship](https://www.youtube.com/@Fireship) - Short videos summarizing frameworks, tools, and engineering concepts.
+- [ThePrimeagen](https://www.youtube.com/@ThePrimeagen) - Streams and clips about developer productivity and tooling choices.
+- [Traversy Media](https://www.youtube.com/@TraversyMedia) - Tutorials on web development stacks and workflows.
+- [Web Dev Simplified](https://www.youtube.com/@WebDevSimplified) - Concept-first videos on frontend and backend development.
+
+## Developer Surveys and Trend Reports
+
+*Annual surveys and reports that track which tools and technologies developers are adopting.*
+
+- [Stack Overflow Developer Survey](https://survey.stackoverflow.co) - Annual report on developer tools, work, and language usage.
+- [State of JS](https://stateofjs.com) - Community survey tracking JavaScript ecosystem adoption and satisfaction.
+- [State of CSS](https://stateofcss.com) - Survey measuring CSS usage, feature adoption, and workflow trends.
+- [RedMonk Programming Language Rankings](https://redmonk.com/sogrady/category/programming-languages/) - Quarterly language ranking based on GitHub and Stack Overflow signals.
+- [GitHub Octoverse](https://octoverse.github.com) - Data report on open source activity and language movement.
+- [Google DORA Report](https://dora.dev) - Research on software delivery practices and engineering performance.
+- [Thoughtworks Technology Radar](https://www.thoughtworks.com/radar) - Opinionated guidance on technologies to adopt, trial, or hold.
+- [SlashData Developer Nation](https://www.slashdata.co/developer-nation) - Global developer population and platform trend research.
+
+## Developer Communities and Forums
+
+*Where developers discuss tech news, ask questions, and share what they are building.*
+
+- [daily.dev Squads](https://docs.daily.dev/docs/squads/creating-your-squad) - Topic and team spaces for sharing developer posts and discussions.
+- [Stack Overflow](https://stackoverflow.com) - Q&A forum for practical programming questions across stacks.
+- [DEV Community](https://dev.to) - Social publishing and discussion platform for software developers.
+- [Hashnode](https://hashnode.com) - Developer community platform with articles and team publications.
+- [GitHub Discussions](https://docs.github.com/en/discussions) - Repository-based discussion threads for product and open source communities.
+- [freeCodeCamp Forum](https://forum.freecodecamp.org) - Community forum for coding learners and mentors.
+- [Indie Hackers](https://www.indiehackers.com) - Community forum for builders working on software products.
+- [Reddit r/programming](https://www.reddit.com/r/programming) - High-traffic programming link forum with community discussion.
+
+## Developer Social Networks
+
+*Professional networks and social platforms built for developers.*
+
+- [app.daily.dev](https://app.daily.dev) - Social feed for following developer content and activity.
+- [GitHub](https://github.com) - Code hosting network with social discovery around repositories and contributors.
+- [X](https://x.com) - Real-time social network used by many developers to share tooling updates.
+- [Threads](https://www.threads.net) - Social feed platform where developers follow creators and product teams.
+- [Showwcase](https://www.showwcase.com) - Social network centered on developer projects and articles.
+- [Mastodon](https://joinmastodon.org) - Federated social network with active developer instances.
+- [Bluesky](https://bsky.app) - Decentralized social platform with growing technical communities.
+- [GitHub Community Discussions](https://github.com/orgs/community/discussions) - Public discussions on GitHub workflows and developer collaboration.
+
+## Browser Extensions
+
+*Extensions that turn your browser into a developer productivity tool.*
+
+- [daily.dev Chrome Extension](https://chrome.google.com/webstore/detail/dailydev-the-homepage-dev/jlmpjdjjbgclbocgajdjefcidcncaied) - Replaces the new tab page with a personalized developer news feed.
+- [React Developer Tools](https://chromewebstore.google.com/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi) - Inspects React component trees and state in the browser.
+- [Redux DevTools](https://chromewebstore.google.com/detail/redux-devtools/lmhkpmbekcpmknklioeibfkpmmfibljd) - Tracks Redux actions and state transitions for debugging.
+- [Wappalyzer](https://chromewebstore.google.com/detail/wappalyzer-technology-pro/gppongmhjkpfnbhagpmjfkannfbllamg) - Detects technologies used by websites.
+- [Lighthouse](https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk) - Runs performance and accessibility audits in Chrome.
+- [JSON Viewer](https://chromewebstore.google.com/detail/json-viewer/efknglbfhodbnglkednfgbflelgjlpja) - Formats JSON responses directly in the browser.
+- [Octotree](https://chromewebstore.google.com/detail/octotree-github-code-tree/bkhaagjahfmjljalopjnoealnfndnagc) - Adds a file tree explorer to GitHub repository pages.
+- [Requestly](https://chromewebstore.google.com/detail/requestly-open-source-htt/mdnleldcmiljblolnjhpnblkcekpdkpa) - Intercepts and modifies HTTP requests for debugging workflows.
+
+## Code Editors and IDEs
+
+*The editors and environments developers use every day to write code.*
+
+- [Visual Studio Code](https://code.visualstudio.com) - Extensible editor for general software development workflows.
+- [Cursor](https://www.cursor.com) - AI-native editor for code navigation and refactoring tasks.
+- [Zed](https://zed.dev) - Fast collaborative editor focused on low-latency coding.
+- [Neovim](https://neovim.io) - Modern Vim-based editor with plugin-driven customization.
+- [Vim](https://www.vim.org) - Modal text editor with a large ecosystem and long-term stability.
+- [IntelliJ IDEA](https://www.jetbrains.com/idea) - Full-featured IDE for JVM and multi-language projects.
+- [WebStorm](https://www.jetbrains.com/webstorm) - JavaScript and TypeScript IDE with integrated tooling support.
+- [Sublime Text](https://www.sublimetext.com) - Lightweight editor optimized for speed and keyboard workflows.
+
+## AI Coding Assistants
+
+*AI-powered tools that help developers write, review, and debug code faster.*
+
+- [GitHub Copilot](https://github.com/features/copilot) - AI coding assistant integrated into common editors and IDEs.
+- [Claude Code](https://www.anthropic.com/claude-code) - Agentic coding tool for repository-level development tasks.
+- [Codeium](https://codeium.com) - Completion and chat assistant for multiple editors.
+- [Tabnine](https://www.tabnine.com) - Code completion assistant focused on privacy and team deployment.
+- [Sourcegraph Cody](https://sourcegraph.com/cody) - Codebase-aware assistant for search, edits, and refactors.
+- [Amazon Q Developer](https://aws.amazon.com/q/developer) - Assistant for coding and AWS workflow tasks.
+- [Aider](https://aider.chat) - Terminal-based coding assistant that edits files from chat prompts.
+- [Continue](https://www.continue.dev) - Open source framework for adding assistant workflows to editors.
+
+## Productivity and Workflow Tools
+
+*Daily tools for staying organized, managing tasks, and working faster in the terminal.*
+
+- [Linear](https://linear.app) - Issue tracking system for engineering planning and delivery.
+- [Notion](https://www.notion.so) - Workspace for project docs, plans, and team notes.
+- [Obsidian](https://obsidian.md) - Markdown-first personal knowledge base for technical notes.
+- [Raycast](https://www.raycast.com) - Command launcher for automating desktop development workflows.
+- [Warp](https://www.warp.dev) - Terminal with modern command UX and collaboration features.
+- [tmux](https://github.com/tmux/tmux) - Terminal multiplexer for persistent and split-session workflows.
+- [Oh My Zsh](https://ohmyz.sh) - Framework for managing shell configuration and plugins.
+- [Alfred](https://www.alfredapp.com) - macOS launcher for keyboard-driven developer productivity tasks.
+
+## Tool Discovery Platforms
+
+*Where developers find and evaluate new tools and frameworks.*
+
+- [daily.dev Explore](https://app.daily.dev/explore) - Topic-based browsing experience for discovering developer tools and articles.
+- [GitHub Topics: DevTools](https://github.com/topics/devtools) - Topic index for discovering active developer tooling projects.
+- [DevHunt](https://devhunt.org) - Product discovery community focused on developer tools.
+- [Console](https://console.dev) - Curated discovery feed for new developer tooling.
+- [GitHub Topic: Developer Tools](https://github.com/topics/developer-tools) - Topic index for comparing active developer tool repositories.
+- [GitHub Topic: Open Source](https://github.com/topics/open-source) - Discovery feed for notable open source software projects.
+- [Best of JS](https://bestofjs.org) - JavaScript project discovery index ranked by activity and popularity.
+- [GitHub Trending](https://github.com/trending) - Daily and weekly list of repositories gaining momentum.
+
+## Job Boards and Career Platforms
+
+*Platforms for finding developer jobs, from junior roles to senior remote positions.*
+
+- [GitHub Topic: Jobs](https://github.com/topics/jobs) - Aggregated repositories and resources related to software hiring.
+- [Arc](https://arc.dev) - Developer hiring platform with remote and contract opportunities.
+- [GitHub Topic: Remote Work](https://github.com/topics/remote-work) - Remote-oriented resources and job-related tooling references.
+- [Remote OK](https://remoteok.com) - Remote job aggregator with developer filters.
+- [Built In](https://builtin.com/jobs/dev-engineering) - City-based technology job marketplace.
+- [Built In Remote Developer Jobs](https://builtin.com/jobs/remote/dev-engineering) - Remote engineering role listings across software companies.
+- [Dice](https://www.dice.com) - Technology career marketplace for engineering and IT roles.
+- [Y Combinator Jobs](https://www.ycombinator.com/jobs) - Startup job board for YC-backed companies.
+
+## Developer Profile and Portfolio
+
+*Tools for showcasing your developer activity and building a professional profile.*
+
+- [daily.dev DevCard](https://app.daily.dev/devcard) - Shareable profile card for presenting developer interests and reading activity.
+- [GitHub Profile README](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile) - Custom profile page for presenting projects and contributions.
+- [LinkedIn](https://www.linkedin.com) - Professional profile network for sharing software experience and project work.
+- [CodersRank](https://codersrank.io) - Developer profile platform powered by public coding activity.
+- [Stack Overflow Developer Story](https://stackoverflow.com/users/story) - Profile format for summarizing technical background and experience.
+- [Dev Portfolio Generator](https://github.com/saadpasta/developerFolio) - Open source starter for building personal developer portfolios.
+- [WakaTime](https://wakatime.com) - Coding activity tracker for generating measurable work summaries.
+- [GitHub Stars](https://stars.github.com) - Program highlighting developer impact and open source contributions.
+- [Hashnode Portfolio](https://hashnode.com/headless) - Publishing setup for turning technical writing into a public profile.
+
+## Learning Platforms
+
+*Free and paid platforms for learning to code and building technical depth.*
+
+- [daily.dev Docs](https://docs.daily.dev/docs/intro) - Documentation hub for learning feed setup, personalization, and product features.
+- [freeCodeCamp](https://www.freecodecamp.org) - Free coding curriculum with projects and certifications.
+- [The Odin Project](https://www.theodinproject.com) - Open curriculum focused on full-stack web development.
+- [Codecademy](https://www.codecademy.com) - Interactive coding lessons across multiple languages.
+- [Frontend Masters](https://frontendmasters.com) - Advanced courses taught by working engineers.
+- [Scrimba](https://scrimba.com) - Interactive video courses with editable code in the lesson player.
+- [Coursera Computer Science](https://www.coursera.org/browse/computer-science) - University-backed courses across software topics.
+- [Khan Academy Computing](https://www.khanacademy.org/computing) - Beginner-oriented lessons for programming fundamentals.
+- [Exercism](https://exercism.org) - Practice-driven learning with mentor feedback across languages.
+
+## Coding Practice and Challenges
+
+*Sites for sharpening your skills and preparing for technical interviews.*
+
+- [Exercism Practice](https://exercism.org/tracks) - Language-specific exercises designed for regular coding practice.
+- [HackerRank](https://www.hackerrank.com) - Programming challenges and skill assessments by domain.
+- [Codewars](https://www.codewars.com) - Kata-based coding exercises with community solutions.
+- [CodeSignal](https://codesignal.com) - Practice and assessment platform for technical hiring preparation.
+- [Project Euler](https://projecteuler.net) - Mathematical and algorithmic programming challenges.
+- [Advent of Code](https://adventofcode.com) - Annual programming challenge event with daily puzzles.
+- [Topcoder](https://www.topcoder.com) - Competitive programming and challenge platform.
+- [CodeChef](https://www.codechef.com) - Contest-based problem solving platform for algorithm practice.
+
+## Books
+
+*Essential books for developers who want to go beyond tutorials and build lasting expertise.*
+
+- [The Pragmatic Programmer](https://pragprog.com/titles/tpp20/the-pragmatic-programmer-20th-anniversary-edition) - Practical guidance for long-term software craftsmanship.
+- [Clean Code](https://www.pearson.com/en-us/subject-catalog/p/clean-code/P200000009529/9780136083238) - Principles for writing readable and maintainable codebases.
+- [Designing Data-Intensive Applications](https://dataintensive.net) - Foundations for data systems and distributed architecture decisions.
+- [A Philosophy of Software Design](https://web.stanford.edu/~ouster/cgi-bin/book.php) - Approaches for reducing complexity in software design.
+- [Staff Engineer](https://staffeng.com/book) - Career guidance for technical leadership paths.
+- [The Missing README](https://www.oreilly.com/library/view/the-missing-readme/9781098123703) - Career and communication handbook for software engineers.
+- [Site Reliability Engineering](https://sre.google/books) - Practices for reliability and operations at scale.
+- [Refactoring](https://martinfowler.com/books/refactoring.html) - Techniques for improving code structure safely.
+
+## See Also
+
+- [Awesome Developer Marketing](https://github.com/dailydotdev/awesome-developer-marketing#readme) - Tools, platforms, and resources for marketing to software developers.
+- [Awesome Newsletters](https://github.com/zudochkin/awesome-newsletters#readme) - Curated newsletters across software and engineering domains.
+- [Awesome Browser Extensions for GitHub](https://github.com/stefanbuck/awesome-browser-extensions-for-github#readme) - Extensions that improve GitHub navigation and workflows.
+- [Awesome Developer Experience](https://github.com/prokopsimek/awesome-developer-experience#readme) - Resources for improving developer experience in products and teams.
+
+## Contributing
+
+Please read the [contribution guidelines](contributing.md) before submitting a pull request.
+
+## Last Verified
+
+2026-02
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000..565bcda
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,36 @@
+# Security Policy
+
+This repository is a curated list, not an application or package. Most security risks here are content risks (for example: malicious links, typo-squatted domains, deceptive redirects, or unsafe contribution patterns).
+
+## Supported Scope
+
+This policy applies to:
+
+- `README.md` entries and outbound links
+- Contribution workflows, issue templates, and automation in `.github/`
+- Any change that could mislead contributors or direct users to unsafe resources
+
+## How to Report a Security Concern
+
+Please avoid posting sensitive details in public issues.
+
+Preferred path:
+
+1. Open a private vulnerability report through the repository **Security** tab (GitHub private reporting).
+2. Include the affected entry/workflow, impact, and reproduction details.
+
+Fallback path (if private reporting is unavailable):
+
+1. Open a public issue with minimal details.
+2. Clearly mark it as a security concern.
+3. Do not include exploit instructions or sensitive data.
+
+## Response Expectations
+
+- Initial triage target: within 7 days
+- Status updates: at least every 7 days while the report is active
+- Fix timing: depends on severity and maintainer availability
+
+## Disclosure
+
+Please allow maintainers time to investigate and remediate before full public disclosure.
diff --git a/code-of-conduct.md b/code-of-conduct.md
new file mode 100644
index 0000000..f243b4b
--- /dev/null
+++ b/code-of-conduct.md
@@ -0,0 +1,127 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and maintainers pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances
+  of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned with this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders by opening an issue in this repository.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.
+
+[homepage]: https://www.contributor-covenant.org
diff --git a/contributing.md b/contributing.md
new file mode 100644
index 0000000..465ebba
--- /dev/null
+++ b/contributing.md
@@ -0,0 +1,70 @@
+# Contribution Guidelines
+
+Please note that this project is released with a [Contributor Code of Conduct](code-of-conduct.md). By participating in this project you agree to abide by its terms.
+
+## Adding a new resource
+
+Please ensure your pull request adheres to the following guidelines:
+
+- Search previous suggestions before making a new one to avoid duplicates.
+- Make an individual pull request for each suggestion.
+- The resource must be specifically relevant to developers staying informed, productive, and growing.
+- Use the following format: `[Name](URL) - Description.`
+- Descriptions should be clear, concise, and end with a period.
+- Descriptions should start with a capital letter.
+- New categories or improvements to the existing categorization are welcome.
+- Check your spelling and grammar.
+- Make sure your text editor is set to remove trailing whitespace.
+- The pull request should include a clear title and a short note on why the resource belongs in this list.
+
+## Trust and safety checks
+
+Before submitting:
+
+- Use canonical HTTPS links (no shortened URLs, no tracking parameters).
+- Avoid links that immediately redirect through ad, affiliate, or unknown tracking domains.
+- If you are affiliated with a resource, disclose that in your PR description.
+- Flag suspicious or potentially malicious links using our security process in `SECURITY.md`.
+
+## Updating your pull request
+
+If the maintainers notice anything that needs to change before merging, we will ask you to edit your pull request. There is no need to open a new one. Please follow the suggestions in [this guide](https://github.com/RichardLitt/knowledge/blob/master/knowledge/github/amending-a-commit-guide.md) on how to update a pull request.
+
+## Issue templates and labels
+
+For non-PR suggestions and maintenance tasks, use the issue templates in `.github/ISSUE_TEMPLATE`.
+
+### Label taxonomy
+
+- `type:suggestion` - New resource suggestions.
+- `type:bug` - Incorrect links, factual errors, or formatting regressions.
+- `type:taxonomy` - Category structure updates and reorganizations.
+- `type:maintenance` - Recurring upkeep work (audits, cleanup, reviews).
+- `area:links` - Broken URL reports and link-quality tasks.
+- `area:categories` - Category placement and naming tasks.
+- `area:content` - Description quality, scope fit, and editorial tasks.
+- `status:triage` - Needs maintainer review and routing.
+- `status:needs-info` - Missing details from reporter.
+- `status:ready` - Clear next action is defined.
+- `priority:high` - Time-sensitive quality or reliability work.
+- `priority:medium` - Important improvements to complete soon.
+- `priority:low` - Nice-to-have backlog improvements.
+
+## What we are looking for
+
+- Reliable sources for developer news and programming updates.
+- Communities where developers actively discuss tools and engineering topics.
+- Browser extensions, editors, and daily workflow tools for developers.
+- Career, learning, and growth resources with practical value.
+- Reports and surveys that help developers understand trend changes.
+
+## What we are NOT looking for
+
+- General tools with no clear developer relevance.
+- Unmaintained, deprecated, or archived projects.
+- Resources behind full paywalls, unless there is a strong reason to include them.
+- Affiliate links, referral links, or URL shorteners.
+- Marketing content disguised as neutral resources.
+- Duplicate entries or tools that replicate an existing entry without clear differentiation.
+
+Thanks for helping improve the list.