# Markdown, Asciidoc, or reStructuredText – a tale of docs-as-code **URL:** \ **Category:** In The News\ **Tags:** markdown, code, in-the-news\ **Created:** [9 November 2022 15:14 UTC](https://forum.devtalk.com/t/markdown-asciidoc-or-restructuredtext-a-tale-of-docs-as-code/82017 "2022-11-09T15:14:02Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![CommunityNews](https://forum.devtalk.com/user_avatar/forum.devtalk.com/communitynews/32/1113_2.png) [@CommunityNews](https://forum.devtalk.com/u/CommunityNews)\ **Post date:** [9 November 2022 15:14 UTC](https://forum.devtalk.com/t/markdown-asciidoc-or-restructuredtext-a-tale-of-docs-as-code/82017/1 "2022-11-09T15:14:02Z")
> Markdown, Asciidoc, or reStructuredText - a tale of docs-as-code. > Who writes the developer documentation for your product? During the early days of my tech career, I worked on a database replication product at IBM. My immediate team had developers and testers but not a single technical writer. I can speak for myself when I say that I never bothered to know who keeps writing the lengthy and complex documentation for every release. Since then, many companies in tech (including companies like IBM) have taken a modern approach to documentation. This “modernization” started when more and more developers started writing documentation (not all developers hate writing docs 🤭). Having git running in their DNA, these developers wanted to bring in collaboration, version control, scripting, and easier bug tracking within developer documentation. Read in full here: > **[Markdown, Asciidoc, or reStructuredText - a tale of docs-as-code](https://www.dewanahmed.com/markdown-asciidoc-restructuredtext/)** > > Who writes the developer documentation for your product? During the early days of my tech career, I worked on a database replication product at IBM. My immediate team had developers and testers but not a single technical writer. I can speak for... _This thread was posted by one of our members via one of our news source trackers._