Contributing to devrel.directory

devrel.directory is an open resource, and contributions from people who do DevRel work are what keep it useful.

What contributions are welcome

• Directory listings: tools, communities, newsletters, podcasts, and agencies for the directory. Submit a listing through the form for a one-time $50 USD payment.
• Job posts: open DevRel roles for the job board. Submit a job for a one-time $50 USD payment. Standard postings run for up to 60 days, subject to the listing remaining open. The optional $149 featured post includes a highlighted placement for 30 days.
• Event submissions: DevRel conferences and meetups for the events page. Submit an event for a one-time $50 USD payment, including its CFP link and deadline when available. Accepted events stay on the upcoming calendar through their event dates; CFPs are shown while their deadlines remain open.
• Listing corrections: email [email protected] with the listing URL and what needs changing, or [email protected] for a job correction. Correcting an existing listing does not require another payment.
• Docs improvements: corrections, sharper examples, or expanded sections anywhere in the knowledge base. Email [email protected] with the page and the change you have in mind.

How changes land

Every submission is reviewed by the maintainer before it goes live, against the criteria published in How we curate - reading that page first is the best way to get a submission accepted. Every new directory, job, or event submission uses its online form and a one-time $50 USD payment through Stripe. Accepted submissions receive a standard listing, and declined submissions receive a full refund. Payment does not guarantee acceptance, preferential ranking, or a favorable editorial assessment. There is no recurring subscription; accepted listings remain subject to the published curation and removal rules. Email remains the contact path for corrections, support, and docs suggestions, rather than a way to submit a new listing without payment. Include the essentials up front - what it is, where it lives, and a line on why it belongs.

The editorial bar

Docs contributions are held to a concrete standard: specific guidance, real examples, numbers where they exist, and honest tradeoffs. Generic filler that could appear on any site gets rejected, even when it is well written. The bar is strict for a structural reason: every docs page ships verbatim into the site's AI-facing mirrors at /llms.txt and /llms-full.txt, and each page is served as raw Markdown at its own .md endpoint. Thin content therefore does not just read badly on the page - it degrades how AI assistants represent the site to developers who never visit it directly.

Getting help

• Email [email protected]
• Message @0xfabs on X