# Developer Experience

- [The Power of Content](https://scribbles.devrel.page/developer-experience/the-power-of-content.md): Tanay from n8n, talks about the power of great content, including its ability to shape the culture of a developer community, and how to approach creating a meaningful content strategy from scratch.
- [Building a Developer Community in an Enterprise World](https://scribbles.devrel.page/developer-experience/building-a-developer-community-in-an-enterprise-world.md): Listen to Laura Cowen as she goes around talking about how she developed a community and DevRel culture in IBM making the organisation understand the needs and expectations of the developers.
- [How to lose a dev in three ways](https://scribbles.devrel.page/developer-experience/how-to-lose-a-dev-in-three-ways.md): Jamie Wittenberg talks about great ways you can incorporate to make your documentation better and more accessible to new developers.
- [Developer relations, why is it needed?](https://scribbles.devrel.page/developer-experience/developer-relations-why-is-it-needed.md): Explaining your role and function comes with the territory of working in this space, but why is that? It’s tricky to define, describe what developer relations is, and why it even exists?
- [The hierarchy of developer needs](https://scribbles.devrel.page/developer-experience/the-hierarchy-of-developer-needs.md): Mike Stowe takes a look at the Hierarchy of Developer Needs, and how you can use it to balance your efforts and ensure your users are successful.
- [GitHub is your documentation landing page](https://scribbles.devrel.page/developer-experience/github-is-your-documentation-landing-page.md): Lorna Mitchell covers what it takes to create a README that engages and informs developers.
- [Docs as engineering](https://scribbles.devrel.page/developer-experience/docs-as-engineering-an-intro-to-developer-experience-engineering.md): Cristiano Betta shares the practicalities of how they have taken an engineering approach to their API documentation.
- [Commit messages vs. release notes](https://scribbles.devrel.page/developer-experience/commit-messages-vs.-release-notes.md): Can you make good release notes by collating your commit messages? Eva Parish argues not. Eva Parish explains the different purposes of commit messages and release notes.
- [A11y pal(ly)- crafting universally good docs](https://scribbles.devrel.page/developer-experience/a11y-pal-ly-crafting-universally-good-docs.md): Google’s Sangeetha Alagappan talks about making your docs inclusive, what accessibility means in the context of documentation, and common pitfalls you might encounter.
- [Inspiring and empowering users to become great writers, and why that’s important](https://scribbles.devrel.page/developer-experience/inspiring-and-empowering-users-to-become-great-writers-and-why-thats-important.md): In this talk from DevRelCon London 2019, Jo Cook talks about The Good Docs Project and Google’s Season of Docs are working to make it easier to create excellent open-source documentation.
- [Solving internal technical documentation at Spotify](https://scribbles.devrel.page/developer-experience/solving-internal-technical-documentation-at-spotify.md): Gary Niemen share their story of how their approach to documentation has changed at Spotify, drawing parallels with Joseph Campbell’s Hero’s Journey framework.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://scribbles.devrel.page/developer-experience.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.