A curated list of developer resources on the .dev TLD, inspired by awesome.re.

• crm.dev - homepage for the Salesforce developer program
• glitch.dev - the Glitch guide to developer relations
• nodejs.dev - Node.js guide content
• opensource.dev - Google’s guide to open source
• stripe.dev - Stripe demos, guides, and developer tools
• slack.dev - Slack tools, libraries, and SDKs
• web.dev - educational resources about web development from Google
• ycombinator.dev - Y Combinator Resources for Developers
• kapitan.dev - Generic templated configuration management for Kubernetes, Terraform and other things
• tfhub.dev - TensorFlow hub
• pptr.dev - a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol
• awesomestacks.dev - an open source tool for discovering tech stacks for building different applications and features

• jess.dev - Jess Frazelle's blog
• hashnode.dev - Hassle-free Blogging Software for Developers!.

• women.dev - women Who Code is the largest and most active community for technical women in the world.

• github.dev - personal websites built on your Github data
• grow.dev - a declarative, file-based microsite generator
• agones.dev - host, run and scale dedicated game servers on Kubernetes
• lodash.dev - a modern JavaScript utility library delivering modularity, performance & extras
• asylo.dev - an open and flexible framework for enclave applications
• v8.dev - Google’s open source high-performance JavaScript and WebAssembly engine, written in C++.
• cube.dev - Cube.js, an open source serverless analytics framework

• jetbrains.dev - developer tools
• workers.dev - build & deploy serverless apps on a global cloud network

Please ensure your pull request adheres to the following guidelines:

• The .dev domain needs to host a site itself, not be a redirect to another resources
• Make sure the site is related to developer resources in some way
• Search previous suggestions before making a new one, as yours may be a duplicate.
• Make an individual pull request for each suggestion.
• Additions should be added to the bottom of the relevant category.
• Include a short description for each addition; this is required.
• 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 and commit should have a useful title.
• Thank you for your suggestions!