This is too biased for me IMHO. I do agree with some points, documentation IS amazing, and you are very likely under-documenting things. But documentation is not cheap to create, and specially it's not cheap to maintain. I've worked in multiple companies where the problem was too much documentation, and of course everyone was afraid to update or ghasps remove any piece of old documentation in case it... - Source: Hacker News / about 1 year ago

I have used Markdown before (https://dillinger.io/) so wouldn't have a problem with using it again as long as on page SEO isn't any extra effort. I am not sure how I would use Markdown and then add the content to the blog to be deployed and if that is going to be much harder than a headless CMS, I would go for the headless. Source: 8 months ago

Useful rescources for this are: Markdown Cheatsheet and Markdown Editor. - Source: dev.to / about 1 year ago

-put chatgpt output into dillinger.io and save as markdown file. Source: about 1 year ago

Did you try pasting the response in a Markdown editor and check if it's working? Here's one online - https://dillinger.io/. Source: about 1 year ago

Which works at https://dillinger.io/, but not https://insiders.vscode.dev. Source: about 1 year ago