A Minimalist Blogger, Website Developer and Privacy Enthusiast.

Proud to Be a FOSS User.

I have a Distro-Hopping disease. Currently settled on Archlinux.

Heavy Reader.

Enjoy coding and learn by mistakes.

Extremely Introverted Individual Who Prefers Solitude.

  • 32 Posts
  • 59 Comments
Joined 9 months ago
cake
Cake day: December 9th, 2025

help-circle




  • I use ghostwriter to write blogs in markdown. Then with the help of a converter i convert it into html format and modify it from there.

    Why not directly write in HTML?

    Because for me writing blogs in direct html feels so hard for several reasons,

    • Adding tags every-time affects my writing flow.
    • Markdown is so simple compared to HTML and ghostwriter shows a direct live preview on the side.
    • Markdown to HTML converters work so well by converting the markdown symbols into proper HTML tag.

    But why I may switch?

    I would consider to switch to directly writing blogs in HTML when i have enough knowledge about web development. The reasons are,

    • It is harder to correct or tweak lines of converted HTML, when compared to directly written HTML.
    • Converters are not perfect either, they make mistakes when identifying equivalent tags. Then later it will become a headache to review again and again.
    • Later we have to implement CSS and class by reading each line of converted HTML, which actually doubles the effort.
    • If I learned HTML, CSS and JavaScript well, and get comfort with it, then there is no need to write in Markdown format, use Hugo/Zola, find a good pre-built theme and keep it from breaking, etc. HTML, CSS, JavaScript manages itself everything.
    • Managing our own website and writing blogs in it is actually very interesting and exciting than writing blogs in someones else’s template/theme. (No matter we get viewers or not).

    I recommend directly writing on HTML rather than Markdown to reduce the effort needed.

    Thank you for the resources. It looks very helpful.