# Contributing to devrel.directory (https://devrel.directory/docs/additional-resources/contributing)



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

## What contributions are welcome [#what-contributions-are-welcome]

* **Directory listings**: tools, communities, and resources for the [directory](/directory). The submit button on that page opens a pre-filled email with the expected fields.
* **Job posts**: open DevRel roles for the [job board](/jobs). Free community listings go through the submit button there, which pre-fills an email to [jobs@devrel.directory](mailto:jobs@devrel.directory).
* **Employer nominations**: companies that hire in DevRel but are not being watched yet. The board is built by re-reading a hand-maintained watchlist of employer job boards twice a week, so nominating a company adds every DevRel role it posts from then on rather than a single listing. [Nominate an employer](/jobs#nominate) from the job board, with the company name and its careers page.
* **Event submissions**: DevRel conferences and meetups for the [events page](/events), via the submit button on that page.
* **Docs improvements**: corrections, sharper examples, or expanded sections anywhere in the knowledge base. Email [submit@devrel.directory](mailto:submit@devrel.directory?subject=Docs%20improvement) with the page and the change you have in mind.

## How changes land [#how-changes-land]

Every submission is reviewed by the maintainer before it goes live, against the criteria published in [How we curate](/docs/additional-resources/how-we-curate) - reading that page first is the best way to get a submission accepted.
Listings, events, and docs suggestions go to [submit@devrel.directory](mailto:submit@devrel.directory); job posts go to [jobs@devrel.directory](mailto:jobs@devrel.directory).
Include the essentials up front - what it is, where it lives, and a line on why it belongs - and it will typically be live within a few days.

## The editorial bar [#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](/llms.txt) and [/llms-full.txt](/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 [#getting-help]

* Email [submit@devrel.directory](mailto:submit@devrel.directory)
* Message [@0xfabs](https://x.com/0xfabs) on X