Moving Config Docs From YAML to Markdown

Documenting configuration directly on the config file is great, right? Everything is right there.

Ehh.

This could probably be repackaged.

Why embark on this journey?

You can Ctrl + F (or Command + F) your way through the file, but you have to know what you are looking for.

You could argue an intuitive experience and naming strategy would work well in this situation, but that's a stretch, particularly when talking about advanced config. A great goal, but really …

documentation journey markdown moving through yaml