Introducing the Markdown Luminary Program: Because It Is Time to Recognise the AI Practitioners

The tech community honours its best. Today, it's time to honour its most prompt-engineered.

The IT world has always known how to celebrate its champions

• Java Champions are recognised for their tireless contributions to the Java ecosystem.
• Oracle ACEs are the trusted voices in database and cloud technology.
• Microsoft MVPs shape communities around .NET, Azure, and beyond.
• AWS Heroes push the boundaries of cloud-native architecture.
• Google Developer Experts drive innovation across Android, Flutter, and ML platforms.

These programs share a common purpose: to identify the people who give more than they take, who show up consistently, who make the rest of us better.

But as I looked at this landscape of recognition, I noticed a gap.

Who is recognising the AI practitioners?

Announcing the Markdown Luminary Program

Today, I am proud to introduce the Markdown Luminary Program: a community recognition program for the AI experts who have weaponized Markdown not just as a file format, but as a way of life. You know who you are:

• You open PRs where the commit message was written by AI in Markdown.
• Your README.md has a Table of Contents. The repo has two files.
• You have a system prompt that ends with "format your response in Markdown."
• You judge other people's commit messages. Silently. But firmly.
• You don't write Markdown. You orchestrate it.

This program is for you.

The Criteria: Are You a Markdown Luminary?

The Markdown Luminary is not given lightly. Candidates must demonstrate sustained excellence across all five pillars of Markdown mastery:

1. 📝 You Generate Markdown

You produce Makdown in docs, notes, wikis, Slack messages formatted with backticks even though Slack doesn't care. If a thought can be written, you write it in Markdown.

2. 🔀 You Push Markdown

Your Git history is a museum. Every file you touch is .md. Your git log reads like a well-organised technical blog. Colleagues clone your repos just to read the commit history.

3. 🔁 You Send PRs on Markdown Files

Others send pull requests on code. You send pull requests on Mardown. You have opened a PR to fix a single Markdown typo in a CONTRIBUTING.md explaining why it matters.

4. ✍️ You Write Commit Messages in Markdown

This is not a commit message. This is literature.

feat(docs): update onboarding README

- Clarified environment setup section

- Added note on .env file requirements

- Fixed broken anchor link in Table of Contents

Refs: #412
        

5. 🧘 You Live the Markdown Philosophy

Markdown is not a tool for you. It is a worldview. Plain text is truth. Structure is kindness. Headers are respect for the reader's time. You texted your mum:

**Mum**, I'll be home for dinner. ETA: **19:30**. Bringing wine. ~~white~~ red.        

She replied "ok honey". You considered adding a > blockquote to her response for context.

How to Apply

It's simple. Your git history is your enemy:

git log --oneline -5        

If fewer than 5 of your last 5 commits are written in Markdown — proper header, structured bullet points, a closing note — close this tab and come back when you're ready.

We will know. The log never lies.

The Badge

All recognised Markdown Luminaries receive the official Markdown Luminary badge — a .png file, ironically — which may be displayed on:

• Your LinkedIn profile (recommended placement: Featured section or About banner)
• Your GitHub profile README (naturally, as an inline image in Markdown)
• Your email signature, where colleagues will ask about it
• Your conference speaker bio, between your job title and your education

The badge is free. The recognition is priceless.