---
title: DXMentorship Sessions
description: How to find, use, and contribute to DXMentorship learning sessions and turn live mentorship into a durable community knowledge base.
url: https://pr-2-5bfc5f2f5cb7.thally.app/dx-mentorship-sessions
---

# DXMentorship Sessions

How to find, use, and contribute to DXMentorship learning sessions and turn live mentorship into a durable community knowledge base.

DXMentorship is built around a simple idea: learning Developer Relations becomes easier when you can learn with people who have done the work.

The public DXMentorship site describes the program as a seven-week Developer Relations mentorship experience designed to help people build skills, confidence, industry connections, and experience through mentors and real-world scenarios.

This page should become the **searchable home for the learning that comes out of those sessions**.

## Start here

- [DXMentorship website](https://dxmentorship.com/)
- [DXM Champions repository](https://github.com/Dxmentorship/champions)
- **Discord/community:** use the current community link published on the DXMentorship website rather than copying an invite that may expire.

## A session should not disappear when the call ends

A useful mentorship session often contains much more than the scheduled topic.

Somebody asks a question. A mentor shares a real example. A tool is demonstrated. A participant mentions an interview experience. A useful framework appears during Q&A.

If all of that stays inside a recording, most of the value becomes hard to find later.

So the session workflow should be:

```text
Live session
      ↓
Recording + notes
      ↓
Key questions and takeaways
      ↓
Resources / examples
      ↓
Guide updates
      ↓
Searchable session archive
```

The documentation and the mentorship program should strengthen each other.

## Suggested session archive

Each session entry should include:

| Field | What to capture |
| --- | --- |
| Session | Clear title |
| Cohort | Which DXMentorship cohort |
| Date | When it happened |
| Mentor / speakers | Names with permission |
| Topic | Main learning area |
| Who it is for | Beginner, intermediate, specific role, etc. |
| Recording | Public link if available |
| Notes | Concise summary |
| Key questions | Useful questions asked during the session |
| Resources | Articles, tools, repositories, slides |
| Related guide pages | Where the learning connects to this handbook |

## Organize sessions by learning need

Chronology is useful, but it should not be the only navigation.

A newcomer is more likely to ask:

> "Where can I learn about DevRel interviews?"

than:

> "What happened in Cohort 4, Week 3?"

So tag sessions by themes such as:

- getting into DevRel;
- Developer Advocacy;
- public speaking;
- technical writing;
- developer experience;
- community building;
- DevRel strategy;
- measurement;
- job search;
- interviews;
- portfolio building;
- leadership.

## Turn repeated mentorship questions into documentation

If the same question appears across cohorts, that is a signal.

For example:

```text
"How do I build a DevRel portfolio?"
        ↓
Asked repeatedly
        ↓
Create or improve Portfolio Project Examples
        ↓
Link it before the next session
        ↓
Use the next questions to improve the page again
```

That is how a living knowledge base should work.

## DXM Champions

The public DXM Champions repository describes a program where community members can participate in organizing and championing a cohort, including moderation and relevant program decisions.

That work deserves documentation too.

Useful records could include:

- what a Champion owns;
- onboarding material;
- moderation guidance;
- cohort operations;
- templates;
- lessons from previous Champions;
- handoff notes for the next cohort.

This reduces the amount of community knowledge that lives only in somebody's head.

## Session publishing checklist

- [ ] The title explains what the learner will get.
- [ ] Mentor/speaker names and links are accurate.
- [ ] Recording permissions are clear.
- [ ] The summary captures useful ideas, not a transcript dump.
- [ ] Resources mentioned in the session are linked and checked.
- [ ] Repeated questions are routed into guide improvements.
- [ ] Private participant information is removed before publishing.
- [ ] The page points to the current DXMentorship community links.

## Archive status

The repository and current public sources do not yet provide a complete, verified session list with dates, speakers, recordings, and slides. The table above is ready for that material, but publishing guessed entries would make the archive less trustworthy.

Add a session when its title, date, speaker, topic, public recording or resource link, and publication permission are confirmed. Link to an existing public recording instead of re-uploading it.

{/* CONTRIBUTOR REVIEW: Add the verified cohort/session archive. Do not publish private recordings, participant names, or community messages without permission. */}

## Related pages

- [Community Authors](/community-authors)
- [What is DXMentorship?](/what-is-dxmentorship)
- [How to Contribute](/how-to-contribute)