devrel.directory is back

The quiet part first

The last post on this blog went out in November 2024, and then the site sat still for over a year and a half. The reason is boring: other work took my hours, and this project got none of them. People kept landing on the guides the whole time, which made the gap harder to ignore. A site called devrel.directory without an actual directory is a bad joke, and I got tired of being the punchline.

So instead of quietly resuming posts, I rebuilt the place. Here is what changed.

A new design

The site is dark by default now, with a single blue accent and a calmer layout across every page. Less decoration, more reading. The homepage finally shows what lives here: the docs, the blog, the changelog, and the newest posts.

The Directory

There is an actual directory at /directory now. It is a curated map of the DevRel ecosystem: tools, communities, newsletters, podcasts, and agencies. Curated is doing real work in that sentence. I only list things practitioners actually use, not everything with "developer" somewhere in the pitch. You can filter by category or search across names, descriptions, and tags, and every listing links straight to the resource itself.

The Jobs board

DevRel roles are scattered across generic job sites where "developer advocate" means five different things. The jobs board fixes that for this corner of the industry: open roles in advocacy, community, docs, and DevRel leadership, each linking straight to the official posting. Community listings are free and stay live for 60 days. If you are hiring and want more reach, featured posts get pinned on top, highlighted, and shared with the audience here.

AI-friendly docs

A growing share of developers meet documentation through an AI assistant before they ever open a browser tab, and DevRel content should practice what it preaches. So the whole knowledge base is machine-readable: an llms.txt index, the full docs as one markdown file, and every docs page available as raw markdown by appending .md to its URL. Each docs page also has quick actions to copy it as markdown or open it directly in ChatGPT, Claude, or Cursor. If you are doing DevRel for a developer product and have not set this up for your own docs, consider this a nudge.

What "the main place for DevRel info" means

That is the claim in the site description, so let me say what I actually mean by it.

A living directory. Listings get added through submissions, reviewed, and pruned when a tool dies or a community goes quiet. A directory that only grows is just a graveyard with good SEO.

Deeper guides. The docs are moving from overview pages toward reference material you come back to while doing the work, like the new practice guides on activities, community building, and content. More of that is coming, and the big narrative pieces will keep landing here on the blog.

Community submissions. Both the directory and the jobs board take submissions through structured GitHub issue forms, and every submission gets reviewed before it goes live. You do not need to know me or write a PR to get something good listed.

And you do not have to check back manually: there is an RSS feed with every blog post, linked in the footer. A proper newsletter is also on the list, and I would rather ship it properly than promise a date here.

If you want to help

The relaunch is the starting line, not the finish. Three things you can do today:

• Know a tool, community, newsletter, podcast, or agency that belongs in the directory? Submit a listing.
• Hiring for DevRel? Post your role for free.
• Want to follow along? Subscribe to the RSS feed, watch the changelog, or follow me on X.

Good to be back.