Monospace font in the Markdown-only editor

I’m still wondering wouldn’t the most obvious solution be not using monospace at all. And use simple component when monospace is wanted.

But I see the difference of policy here:

  • markdown is for devs and coding
  • rich editor is for everyone else
  • if one is member of everything else and likes to use markdown, then must choose

What I really don’t understand is there real need and demand to offer monospace when creating content for writing, that is shown using totally different font.

What bugs me a lot is again feeling that something is again done by drawing border between devs and common people — but perhaps devs are a majority globally — but that feeling is propably just my issue, because everyone elese in this topic are totally happy (if font size question can be fixed).

Well, very academic topic for me, because on my forum that CSS-trick works, and my users don’t need this magnitude pointer to tell which one, markdown or rich one, they are using. And because I have feeling that meta about why and what it gives aren’t wanted or needed, it is better for everybody that I jump off — because after all, I’m not a dev and I don’t need coding/code editor, but markdown editor for content.

4 Likes