[Brajeshwar]

After many iterations of tools, systems, and processes, I have settled on writing in plain text, in Markdown, to identify headings, paragraphs, quotes, images, etc.

My reasoning and approach is that I or someone should be able to read it as it is and then have a tool parse it to spit out HTML for browsers, helping others read it with a better experience.

With thousands of posts, it would be complex for me to maintain them in HTML. Now, my blog is powered by Jekyll because of GitHub pages. However, I can quickly switch to any other tool with minor tweaks.

Locally, I see my blog posts as individual files with dates `YYYY-MM-DD` and the title in their yearly folder `YYYY`. Some are in `WIP`, which I can continue to update/write. The `future` folder contains the ones that are drafts, but I can see them and don't mind if someone stumbles on them. Always a work in progress and am even aiming to simplify it further.

[austin-cheney]

I want to agree with this because I completely love markdown and it solves for so much of accessibility.

Markdown makes it challenging to write form controls (input. select, textarea, buttons) and non-visual identifiers (id, class). To solve for most of these concerns I still find I prefer to do it dynamically against the DOM as needed by user interaction.

[est]

same here.

Besides you can directly embed any HTML inside markdown.