What MkDocs does with a Markdown file, and where an audio recording fits

MkDocs takes Markdown through a file under the docs directory, listed in the navigation of the configuration file, and that is the door this page is about. The question worth asking is what an audio recording looks like by the time it arrives, because MkDocs never sees the recording itself. It sees whatever the conversion handed over, and nothing else.

MkDocs builds the left hand navigation from the configuration and the page contents list from the headings. What comes out of an audio recording here is the speech as punctuated paragraphs, cut where the speaker actually stopped, so the structure MkDocs is looking for is actually present instead of merely implied. That is the entire trick, and there is nothing clever underneath it.

What survives from an audio recording into MkDocs

The conversion drops silence, room tone, and the stretches where nobody says anything at all before MkDocs ever sees them, because none of it carries meaning into MkDocs and all of it costs something. What it keeps is the part you would otherwise have retyped by hand.

• The words come through punctuated, which is most of the work, and MkDocs receives it as structure rather than as something to infer.
• The breaks between turns of speech are kept, so a handover is visible, which is the part MkDocs would otherwise have to reconstruct on its own.
• Figures said out loud are written as digits rather than spelled out, so nothing downstream of MkDocs has to guess at it.

What MkDocs never gets back from an audio recording

Every conversion costs something, and a page listing only the gains is a sales page. Here is what an audio recording gives up on the way to MkDocs, stated plainly enough that you can decide against it.

• Tone, emphasis and hesitation are gone, and they often carried the meaning, and MkDocs will not get it back from anywhere.
• Speaker names are not attached, because nothing in the audio declares them, so nothing you build in MkDocs should depend on it.
• The recording itself is not kept, so the transcript is all there is afterwards, which is a real cost inside MkDocs and not a rounding error.

The Audio to Markdown step behind this MkDocs page was measured

Groq does the conversion, and it was proven end to end on 30 August 2026: a recording made for the occasion, never transcribed anywhere before, came back with its witness word and its figure, split into two turns of speech. That is one run on one day and not an average, which is exactly why the date travels with the claim instead of being left out of it. The same output is what MkDocs would have received.

A crowded room and a cheap microphone cost accuracy, and nothing in the output marks which words were guessed. MkDocs has no way of telling you any of that from the inside, so it gets said here instead, on the page that sent you there.

Once the recording is Markdown, what to do inside MkDocs

With the Markdown in hand, add the page to the navigation in the same change that adds the file, or it is invisible. That is a MkDocs habit rather than a conversion setting, and it is where most of the value of converting an audio recording in the first place actually lands.

The constraint worth knowing before you start: a page missing from the navigation is still built, but unreachable except by direct link. It bites the same way whether the Markdown came out of an audio recording or out of something else entirely, but it bites hardest on long documents, which is what an audio recording usually is.

What we will not pretend about Audio in MkDocs

• MkDocs will not warn about a heading level that skips a rung, and converting an audio recording first does not change that in the slightest.
• two top level headings in one file produce a contents list nobody can follow, which is a MkDocs behaviour rather than anything the recording conversion did.
• The conversion costs half a credit and the price is shown before the recording is sent, whether the Markdown ends up in MkDocs or nowhere at all.