Forem: Patrick Woods

APIGTM: a bunch of lightning talks about APIs + AI

Patrick Woods — Fri, 19 Sep 2025 17:32:46 +0000

We're live-streaming 14 talks about API growth in the age of AI

If you care about driving adoption of your public APIs, I'd love to see you there.

APIs. MCP. Agents. We'll cover it all, along with:

Battle-tested API playbooks from leaders at Canva, Mintlify, Block, WorkOS, Merge, Continue, and more
Techniques on positioning, pricing, and onboarding
Making your endpoints irresistible to developers and AI Agents today, and into the future
Proven tactics for converting word-of-mouth into revenue, and turning casual users into evangelists
The evolving role of MCP and Agents in API GTM strategies

📅 The details

October 7
Noon till 4pm PT
Streaming live from Postman's SF HQ
In-person happy hour to follow
✨ It's free ✨
Signup

🎤 Hear from leading experts on API Growth

Keynote: Ankit Sobti, Co-founder and CTO, Postman
Ernan Anguiano, Product Manager, Firebase
Paige Bailey, Developer Relations Engineering Lead, Google DeepMind
Brian Davidson, Sr Customer Eng, Google Maps
Brian Douglas, Head of Developer Experience, Continue
Nour Eldifrawy, Product Manager, Merge
Meredith Hassett, Sr. Developer Advocate, Canva
Rebecca Hauck, Postman Leader, Lead Technical Product Manager, PayPal
Pratham Kumar, Dev Rel Manager, APILayer
Richard Moot, Tech Lead, Developer Relations at Block
Chris Riley, Sr. Manager, Developer Relations, Hubspot
Paulomi Shroff, Head of AWS Marketplace International Expansion, Amazon
Tobin South, VP of AI Agents, WorkOS
Brandon Waselneck, Head of Product, Mintlify

// Detect dark theme var iframe = document.getElementById('tweet-1968748838111392240-827'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1968748838111392240&theme=dark" }

🚀 Brought to you by the Postman API Network

You're not maximizing your API's potential if developers can't find or successfully use it. Ship your API to millions of developers, onboard them quickly with fewer errors, and drive sustained adoption with actionable usage insights.

Learn more about growing your API usage with the Postman API Network: https://www.postman.com/publish/

Developer Love #1: Unintentional Gatekeeping with Brian Douglas of GitHub

Patrick Woods — Thu, 23 Jul 2020 19:20:32 +0000

In this inaugural episode of Developer Love, host Patrick Woods speaks with Brian Douglas of GitHub.

They discuss the developer advocate role, leveraging open source knowledge, and improving inclusivity within communities.

🎧 Listen now

In this episode

Brian DouglasFollow

Brian founded OpenSauced, a platform for turning open source into opportunity. Try it out and let me know what you think.

Slack vs Discord vs Discourse: The best tool for your community

Patrick Woods — Tue, 26 May 2020 15:40:11 +0000

“What platform should I use for my startup’s community? Should I move from Slack to Discourse? Wait...there’s a Discourse and a Discord?”

Now is a great time to build a community online, and there’s no shortage of really great tools to help.

But despite the many options, there’s no single tool to rule them all. There are just too many variables, including community size, engagement model, the size and capabilities of the team building the community, and more.

While there’s no silver bullet for building and growing a community online, there are a few key questions to consider that will help guide your tooling decisions and your Developer Relations strategy.

In this article, we’ll discuss the key factors to consider when choosing a community platform, compare the three most popular options, and make recommendations based on a few different community scenarios.

Jump to these sections:

The TL;DR recommendations
The 3 key factors to consider when choosing
In-depth feature comparison grid
Detailed recommendations

The TL;DR Recommendations

We’ll discuss plenty of details, but here are the high-level recommendations.

Use Slack if…

You want to take advantage of Slack’s large library of integrations, bots (limited to 10 on free plans), or use their no-code workflow builder (only paid plans).
You want threaded conversations in your realtime chat.
You don’t care that only the last 10,000 messages are retained (on free plans).
You and your community members already use Slack for work.

But keep in mind:

On the free plan, Slack only retains the most recent 10,000 messages, which means they automatically archive messages above that threshold.
Slack paid plans start at $8 per user per month. Every community we’re aware of uses the free plan. Compare Slack pricing plans here.
Slack offers no real tooling for moderation. It’s specifically designed for workplaces, and they don’t appear interested in building features for moderation.

Use Discord if…

You need realtime chat with advanced permissions and moderation.
You need unlimited message history.
Making users sign up for yet-another-Slack group is a concern.
Integrations and bots are less important.
Your community won’t mind the casual gamer-centric aesthetic.

But keep in mind…

With Discord, community members use a single account to login to multiple communities. This user model means you can join new communities with a single click (versus creating a new user account for every community). But it means it’s impossible to use different avatars for different communities, which could be a concern for folks who have used Discord primarily for gaming in the past. It’s possible that some might not want to use their stormtrooper headshot in a professional setting.
Discord’s design and copy is playful and gamer-centric, which could be confusing for community members who aren't familiar with Discord’s gaming roots.

Use Discourse if…

Many community members will likely have similar questions or issues, and you’d like to point them to a library of common answers
You’d like community-generated content to be indexed (and thus findable in search engine results). This helps new members discover the community while reducing the core team’s support burden.
Moderation and fine-grained permissions are important.
You have enough community members for chat to be counterproductive.
Synchronous communication isn’t important, for example, if your community is distributed across many time zones.
You don’t mind paying to host the forum software, or are capable of hosting it yourself
You want to use an open source platform.

But keep in mind…

There are many technical options for starting a community on Discourse, including deploying the open source code on your own servers, paying a third party for hosting, or paying Discourse.org for a fully hosted solution.
For new members, starting a new thread in a forum can be perceived as a higher barrier of entry, versus simply saying “hello” in a chat channel.

Use both chat (Discord or Slack) + Discourse if…

You want indexed content (Discourse) along with realtime vibes (chat).
Have the bandwidth to manage multiple platforms.
Want separate spaces for distinct groups, for example a chat for your champions and a forum for everyone else.
Note: Discourse offers a plugin for integrating with chat platforms.

Three key factors to consider when choosing a community platform

When picking a platform, you’ll likely weigh some factors more heavily than others based on your situation. The factors here will provide you with a framework for assessing the options.

The size of your community

Starting from scratch (or close to it)

In the early stages of a community’s life, it’s important for the organizers to build strong connections with the first handful of members, since early adopters are more likely to join discussions, answer questions, and contribute in ways that make the community seem active and vibrant. Chat is good for this. Scalability and governance are less of a concern at this stage.

Hundreds of community members

At this point, chat platforms can start to feel unmanageable for a few reasons. First, moderation becomes an issue, since it’s hard for a small group of community managers to keep up with the volume of conversations happening (Discord beats Slack on this point).

Second, most community members complain that, on chat platforms, they often answer the same question or address the same concern many times over. The conversations just disappear too quickly for others to easily find, and since they’re not indexed or perma-linked, it’s difficult to reference previously answered questions.

Many thousands of community members

For large, well-established communities, forums are often the right choice, since live chat is difficult to manage and large scales.

Discourse provides fine-grained permissions and moderation that large communities will appreciate. Additionally, since large communities create lots of content, they especially benefit from indexed and shareable content.

One caveat for large communities: big communities are often staffed by large teams, which means they may have the bandwidth to manage more than one platform, such as a forum _and _a chat tool.

The size of your team

Your choice of community platform should take into account your team’s ability to manage multiple channels, their timezone availability, and the number of folks available to interact on your chosen platform—all of which are a function of the team’s size.

Small teams

Small teams tend to start with a single platform, since that’s what they can manage given their bandwidth. In general, teams of three or smaller should commit to a single platform to focus their time and keep overhead low.

Medium teams

These teams are more self-sufficient compared to small teams and won’t need to depend as much on other teams for support. They may be able to handle multiple platforms, but often choose to go deeper with a single platform, such as more clearly defining roles and responsibilities within the team, and designating team members to focus on specific parts of the platform.

Large teams

Larger teams can handle multiple platforms and different sub-communities, such as a Slack for your MVPs and a Discourse forum for everyone else—but doing so introduces substantial overhead in terms of process management, identity resolution, and governance. That said, larger teams inside bigger companies tend to be better equipped to plan for and manage these situations.

Your community’s engagement model

What are the behaviors and norms you want your community members to model? Are you hoping for a casual vibe where members can congregate, discuss, and debate? Or are you more interested in cultivating deep knowledge sharing and collaboration? Once you decide, you should factor your engagement model into your tool choice.

In People Powered, Jono Bacon outlines three engagement models that we think are useful to consider when choosing a platform:

Consumers

These communities revolve around ephemeral and emergent discussions about common interests, and emphasize connection based on those topics. Examples include communities about art, gaming, or general technology trends.

Champions

In this engagement model, community members share knowledge and insights about a common tool or technology, with an emphasis on leveling-up one’s expertise and experience. Members often teach each other through demos and examples, driving further participation from other community members.

Examples include company-specific communities, like the Roam Research Slack group, where members share custom CSS and browser extensions as well as how-to videos to share their knowledge and help others excel.

Collaborators

In communities of collaborators, members work together on shared projects. The primary example is open source software, where diverse people from around the world work together to build and improve a common codebase.

Comparing Slack, Discord, and Discourse

In addition to the key factors above, it’s important to understand the actual feature set each platform offers. The grid below assumes features for the baseline plans for each platform, and includes call-outs when features are offered only on paid tiers.

›› View the full image
›› Download the PDF

Detailed Recommendations

We’ll now look at detailed recommendations based on the key factors and the pros and cons of each platform.

Of all the factors to consider, we think a community’s engagement model should have the most influence over which platform is used, so we’ve organized this section along those lines with caveats for size of community and team.

Consumer communities

Suggestion: Discord

Rationale

Casual communities should lower the barrier to involvement and focus on building close connections between users. For those reasons, we suggest using Discord. With Discord, new members can join with the click of a button (versus creating new accounts, as with Slack and Discord), which means they can get started quickly.

For servers managed by an official brand account, Discord also offers a verification program, which unlocks additional features, like custom branding and short URLs, a verification check mark, and higher quality voice service.

Tradeoffs

Discord is strong out-of-the-box, but doesn’t offer the depth of integrations and bots that you get with Slack. Additionally, content isn’t public and indexed, as with Discourse, though public content isn’t always as important for casual communities compared to the other engagement models. Finally, the gamer aesthetic can be polarizing, depending on the culture of the community members.

Champion communities

Suggestion: Slack

Rationale

Champion communities need to strike a balance between causal connection between members and deeper sharing of information, learning, and projects.

For those reasons, we suggest Slack. It’s widely adopted and understood, and enables the real-time communication crucial to building loyalty among community members. Threaded chats enable community members to follow interesting digressions without distracting the whole channel, and link unfurling makes shared content standout in the flow.

Finally, Slack offers tons of integrations that are useful for sharing work, like the GitHub and Trello integrations.

Tradeoffs

Slack will let you go fast early in the life of your community, but expect to hit a wall around 1,000 active users. At that point, you’ll likely want better moderation and permissions, and you’ll start to bump up against Slack’s 10,000 message retention limit.

From a community member standpoint, it’s annoying to create a new account for every Slack community you join, and for Slack to force you through the same onboarding, even if you’re already a member of dozens of other groups.

So why start with Slack? It takes most communities years to grow to thousands of members, if they make it there at all. That said, given Slack’s ease of startup and widespread adoption, it makes sense to take advantage of it for the speed early on, then consider a transition plan in the future once the pain points become prohibitive.

Collaboration communities

Suggestion: Discourse

Rationale

Communities focused on collaboration usually want to foster deeper participation from existing community members, lower the bar for new folks to get involved, solve problems as a group, and publicly share the solutions.

Discourse stands out in each of these areas. Since all content is public and indexed by search engines, members can reference previously answered questions and discussions, which means the core team can avoid answering the same questions repeatedly. New members can quickly learn the basics and overcome common challenges, and existing members can pose more complex questions and receive help from the broader community.

Discourse is especially powerful for large communities, which face plenty of challenges related to moderation, permissions, and governance, as well as the difficulty of delivering a great experience for all community members.

To address these challenges, Discourse provides granular permissions and moderation, which enables members of the community to progress to higher levels of access and trust.

For communities backed by medium or large teams, we also recommend implementing a live chat platform in addition to Discourse to foster a closer relationship with core team members, or as we call them, members of their Orbit One.

Tradeoffs

Self-hosted, large Discourse instances require ongoing maintenance and performance tuning, and hosted instances cost money. Managing multiple tools can become burdensome, but as long as the team has the bandwidth, these issues should be solvable.

Conclusion

More communities are moving exclusively online, and more tools for managing online communities emerge each day.

While the landscape of community platforms continues to evolve, Slack, Discord, and Discourse can reliably meet the needs of most communities.

But as much as we love debating the nuances of our tools, we can’t forget that “community" really just means “people.” David Spinks reminds us:

// Detect dark theme var iframe = document.getElementById('tweet-1258879281557454848-732'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1258879281557454848&theme=dark" }

If you’d like help tracking your community’s growth and measuring its ROI—no matter which platform you choose—signup for early access to Orbit.

Have opinions? Share them in the comments 👇

The Observatory #3: Hot takes and cool tools for building community remotely

Patrick Woods — Tue, 24 Mar 2020 22:54:21 +0000

As community leaders grapple with the fallout from cancelled events worldwide, tons of folks have shared in-depth guides and tutorials for ways to move events online.

Below, we've pulled together a few shorter reads—call them hot takes and cool tools—that bring a unique perspective to the conversation and hopefully inspire some creativity and energy for your own communities.

🏎️ On the move

But first, our regular round-up of comings and goings in the DevRel and Community space. Have a tip for us? Drop a note to observatory@orbit.love.

Stefan Judis joins Contentful as head of DevRel from Twilio (more).
Vishwa Mehta joins Hasura as as Community Associate (more).
Domitrius Clark joins Cloudinary as Advocate Engineer (more).

The 🔥 takes and ❄️ tools

Have you tried AuxParty? It's a super fun social listening room where you can enjoy music live-curated by others, or step up to the DJ booth yourself.

👌 Try spinning-up a room and asking community members to take turns DJing throughout the workday.

Speaking of jams, TIL how to add a little ambiance to status meetings:

// Detect dark theme var iframe = document.getElementById('tweet-1241120485397549056-201'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1241120485397549056&theme=dark" }

I for one am looking forward to surprising, even delighting, our community members with unexpected background music on future calls.

The biggest question now will be how to pair Zoom background music with the perfect Zoom background image. To spruce up your space, check out this Zoom background gallery from Unsplash 🖼️

While we're at it, I'd like to give Josh a shoutout for always staying way ahead of the curve, and using Zoom backgrounds well before they were cool:

// Detect dark theme var iframe = document.getElementById('tweet-1204438096214818816-15'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1204438096214818816&theme=dark" }

On a more serious note, as more events move online, though, organizers need to stay vigilant against bad actors. As we've seen, lots of folks are hosting large Zoom events without realizing these potential risks, so here's a 🧵 about how to configure Zoom for community safety:

// Detect dark theme var iframe = document.getElementById('tweet-1240073789586714626-513'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1240073789586714626&theme=dark" }

Finally, everyone's trying to figure out how online events can create the impact of their offline counterparts. For many, the answer seems to be something like, "The same great content, now online!"

But David Spinks challenges community leaders to reimagine events for our new online reality:

// Detect dark theme var iframe = document.getElementById('tweet-1238207050410319872-621'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1238207050410319872&theme=dark" }

I hope you've enjoyed these tips and takes. If you've come across something interesting or useful we should share, please post in the comments.

📐 Measure your community with this Orbit Model Airtable template

Measuring community ROI has always been a crucial topic among DevRel and community practitioners, but with the specter of tightening budgets on the horizon, the best teams will find ways to clearly demonstrate their impact.

That's why we made this detailed Airtable template to help communities measure their impact, communicate their value, and focus on what's working for their communities.

Read the blog post and download the template 🚀

What tips or resources have we left out?

Share your own advice for building remote community in the comments below, and please reach out to us at observatory@orbit.love if we can be helpful in any way 💜

🗞️ Previous editions

Don't miss the next edition of The Observatory 🔭

Subscribe here to get an email for each new edition.
Follow Orbit on DEV to see all of our posts.

The Observatory #2: What's in it forum me?

Patrick Woods — Fri, 06 Mar 2020 02:34:59 +0000

In this issue, we shout-out DevRel leaders on the move, hear from Orbit CTO about Orbit and Funnel on a podcast, and take a look at some perspectives on forums for community building + some bonus Slack emoji 🥳

🏎️ On the move

In each issue, we'll highlight key moves in the DevRel and Community space. Have a tip for us? Drop a note to observatory@orbit.love.

Kim Maida joins Gatsby as Head of Developer Relations from Auth0 (announcement)
Jeremy Meiss joins CircleCI as Head of DevRel & Community from Solace (announcement)

🎧 Orbit on the airwaves

Tune in to this podcast for favorite Orbit Model hits, including:

software is not sold, it's adopted
funnel is a model for capturing value for the company; Orbit is a model for creating value for the community
the Orbit Model gives us a language for describing the complex experience of community

DevRel Metrics: Orbit and Funnel

SlashData Team ・ Feb 27 '20

#devrel #podcast

🙊 What's in it forum me?

In our recent chats with leaders of dev communities, we've noticed more discussion around transitioning online conversation from realtime tools like Slack to persistent forums like Discourse.

Forums offer communities lots of benefits, like nuanced permissions and moderation, badges and progress tracking, and the added benefit of content that's both referencable and SEO-able.

We'd love to hear from you about your perspective on forums for building high gravity communities.

To start the conversation, here's a comprehensive overview to get everyone on the same page: Everything You Need To Know About Building Your Online Community Forum (warning: it's a little Vanilla Forums-heavy, but the principles are still instructive).

But does forum = community? Catch up on the discussion in the CMX Facebook group with this question: Can you share the difference between an online community and online forum?

👇 Discuss below

What are some examples of effective developer community building through forums?
What are some common forum pitfalls?

Bonus round: Grab these 🔥 custom Orbit icons for your Slack

// Detect dark theme var iframe = document.getElementById('tweet-1232698780509704193-833'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=1232698780509704193&theme=dark" }

🗞️ Previous editions

The Observatory #1: High Gravity

Don't miss the next edition of The Observatory 🔭

Subscribe here to get an email for each new edition.
Follow Orbit on DEV to see all of our posts.

5 Writing Books Every Technical Leader Should Read

Patrick Woods — Wed, 17 Apr 2019 16:55:34 +0000

Clear and persuasive writing is essential for effective leadership, but most of us have never had any training aside from maybe an English Lit class in college. And yet, writing is a big part of the job. Emails, presentations, articles, and talks are all opportunities to inspire and inform—and they all begin with writing.

You write every day, so maybe you should see yourself as a writer. That may sound scary, but you don’t need an MFA to improve your writing skills.

I’ve read more than a dozen writing books in the past six months, and want to share the five that rise to the top as particularly useful for anyone that uses writing to encourage and educate.

Writing Tools: 50 Essential Strategies for Every Writer

by Roy Peter Clark
📚get it

“Think of writing as carpentry, and consider this book your toolbox. You can borrow a writing tool at any time, and here’s another secret: Unlike hammers, chisels, and rakes, writing tools never have to be returned. They can be cleaned, sharpened, and passed along.”

Clark’s 50-tool list is immensely useful and applicable, and provides an excellent foundation for anyone reading about writing for the first time. Every chapter plainly states a rule, unpacks it over several pages with explanation and example, then concludes with in-depth “workshop” exercises for immediately applying the tool.

And since most rules can be read in less than five minutes, this book is ideal for the busy leader.

Start here, and equip yourself with a powerful framework for deeper exploration.

The Sense of Style: The Thinking Person's Guide to Writing in the 21st Century

by Steven Pinker
📚get it

“Good writing starts strong. Not with a cliché (“Since the dawn of time”), not with a banality (“Recently, scholars have been increasingly concerned with the question of...”), but with a contentful observation that provokes curiosity.”

You might be familiar with Pinker’s popular works, like Enlightenment Now and Better Angels of our Nature, but the Harvard linguist and cognitive scientist has also written a practical guide for the nonfiction writer.

Pinker describes the aspects of what he calls classic style, which emphasizes clear, direct, and powerful language, making it perfect for business writing.

Pinker says, “The guiding metaphor of classic style is seeing the world. The writer can see something that the reader has not yet noticed, and he orients the reader’s gaze so that she can see it for herself.”

What if you could say the same about your writing?

Along the way, he provides and updated grammar, with an emphasis on the functional roles of different parts of speech. Trust me: it’s interesting and useful!

On Writing Well: The Classic Guide to Writing Nonfiction

By William Zinsser
📚get it

“The secret of good writing is to strip every sentence to its cleanest components.”

First published in 1976, On Writing Well continues to dispense practical advice for writers. Its author began his career as a journalist for the New York Herald Tribune, and has enjoyed decades of success as a writer, editor, and educator. This book pulls from that vast experience.

On Writing Well covers useful advice on tone and style, and digs into various nonfiction forms, such as literary nonfiction and sports writing. While many of those sections may not seem applicable to, say, a CEO, the principles are timeless, and provide a unique perspective not found in the typical business book.

Everybody Writes: Your Go-To Guide to Creating Ridiculously Good Content

by Ann Handley
📚get it

“Good writing serves the reader, not the writer. It isn't self-indulgent. Good writing anticipates the questions that readers might have as they're reading a piece, and it answers them.”

Ann Handley provides several chapters on structure and style, but the key difference from other books listed here is her chapters covering brand journalism and channel-specific tips about blogs, tweets, and other social platforms.

This detailed exploration of the nuances of each channel provides leaders with a thorough understanding of how readers experience their messages in various contexts.

Draft No. 4: On the Writing Process

by John McPhee
📚get it

“Writing is selection. When you are making notes you are forever selecting. I left out more than I put down.”

Nonfiction master John McPhee has written for Time, The New Yorker, and has authored many best-selling narrative nonfiction books. True to form, Draft No. 4 contains essays on topics including story progression, the structure of your story, frames of reference, and more.

While the other books on this list read like handbooks, Draft No. 4 feels like a slow walk through the park with a guru. As a result, you’ll absorb his principles through his stories as the main points sneak up on you chapter after chapter.

While most people don’t write essays for The New Yorker, McPhee’s masterclass on narrative provides a compelling perspective on storytelling that promises to add both style and substance to any leader’s writing.

Smart Reading is Essential to Better Writing

Stephen King says that, “If you want to be a writer, you must do two things above all others: read a lot and write a lot.” If that’s true, then reading about writing is like a double bonus for those looking to improve their writing skills. Reading these books will guide your learning and motivate you to explore new ways to influence and inspire with your writing.

What else would you add to the list?

Cover photo: Susan Yin on Unsplash

Help build a list of awesome .dev sites

Patrick Woods — Wed, 20 Feb 2019 19:56:28 +0000

The .dev TLD has created lots of conversation in the community (here and here for example), and some of the most interesting developer-focused companies are using .dev to share dev-focused resources and tools 🛠.

We thought it would be fun to build a list of interesting developer resources on the TLD as they emerge.

orbit-love / awesome-dot-dev

A list of awesome developer resources on the .dev TLD

awesome .dev sites

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

Sites

Resources

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

Blogs

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

Communities

women.dev - women Who Code is the…

View on GitHub

The list is thin for now, but with the community's help, we hope to see the resource grow. Check out the contribution guidelines and add to the list!