mvp

Not the author, but thought it was pretty nice. - https://github.com/DigitallyTailored/Classless.css I know this isn't the first, I have this note from a previous HN discussion: - https://github.com/andybrewer/mvp - https://github.com/kognise/water.css - https://github.com/xz/new.css - https://github.com/vladocar/Basic.css - https://github.com/oxalorg/sakura - https://github.com/igoradamenko/awsm.css - https://github.com/hawkz/gdcss - https://github.com/emareg/classlesscss - https://github.com/vincentdoerig/latex-css - https://github.com/dbohdan/classless-css - https://picocss.com/examples/preview/ - https://github.com/kevquirk/simple.css Aggregate tool: https://dohliam.github.io/dropin-minimal-css/

You could pay a front end dev to use a preexisting template. Or, you could Google “classless CSS”, if you’re OK writing some HTML. I made a plug and play CSS library here for those that don’t want to write CSS: https://github.com/andybrewer/mvp

Here is small list of other "classless" CSS libraries I have found over the years - https://github.com/andybrewer/mvp - https://github.com/kognise/water.css - https://github.com/xz/new.css - https://github.com/vladocar/Basic.css - https://github.com/oxalorg/sakura - https://github.com/igoradamenko/awsm.css - https://github.com/hawkz/gdcss - https://github.com/emareg/classlesscss - https://github.com/vincentdoerig/latex-css (disclaimer: I am the author)

Hi, author of MVP.css here. For those interested in the discussions around this, please refer to: https://github.com/andybrewer/mvp/issues/26 https://github.com/andybrewer/mvp/issues/2 I would concede that the use of ‘a strong’, ‘section aside’, etc. does require some learning and the styling is perhaps unique, but I don’t think it’s invalid in any way. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/st... > The <strong> HTML element indicates that its contents have strong importance, seriousness, or urgency. In MVP.css links are already in bold by default, so ‘strong’ text inside a link requires more “urgency” than bold text, which is styled as a button. Sure, I’ll grant that it’s atypical, but I don’t think it’s obviously wrong in some way. Same with ‘aside’: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/as... > Th

Having such a stylesheet not automatically work in dark mode defeats the purpose. It says "no classes" but then it demands that you add an invalid attribute on your HTML to trigger it. OK, that's a no for me. Source: https://github.com/andybrewer/mvp/issues/76#issuecomment-121...

https://github.com/andybrewer/mvp/ - Out of the box CSS styling for HTML elements. No class names, no framework to learn.

I say this out of a genuine desire to be helpful, I promise: you wouldn't be translating your Markdown "into CSS", you'd be translating it into HTML, and then optionally applying CSS To your original point, if you want something really simple this might work (haven't tried it, just found it on Google): https://github.com/gomarkdown/mdtohtml And then for CSS, you could drop in something like this: https://github.com/andybrewer/mvp

The trouble with “only semantic HTML” (read: “HTML with no class attributes ever”) is when you try to represent things for which there are no semantic elements defined. I then observe that most projects like this then end up abusing other elements. In this case, the use of <aside> is unequivocally wrong, but https://github.com/andybrewer/mvp/issues/2 was closed in the end simply because there was no way to get what was desired without using class or similar. Other things that are also unequivocally semantically incorrect are the button links (a > b, a > i, a > strong, a > em), and raised text notification bubbles (sup). The first rule of web accessibility is that doing nothing is better than doing the wrong thing. https://www.w3.org/TR/wai-aria-practices/#no_aria_better_bad... explains a bit. There’s a reason why the class attribute exist

Feel free to ask questions or contribute on GitHub: https://github.com/andybrewer/mvp

I style those elements in MVP.css (https://github.com/andybrewer/mvp/)

> I’ve filed https://github.com/andybrewer/mvp/issues/1 about this now. Thank you! I'll take a look today. And pull requests are always welcome.

The treatment of <samp> in mvp.css is incorrect. It’s treating <code> as inline monospace, <samp> as block monospace, and completely ignoring <pre>, which is actually block monospace (with no defined semantics). Rather, <code> and <samp> should both be inline, and placed inside <pre> for block usage. This matters because it’ll mess things up if the stylesheet doesn’t load, as your blocks of code won’t be formatted properly. (I’ve filed https://github.com/andybrewer/mvp/issues/1 about this now.) https://chrismorgan.info/blog/rust-fizzbuzz/ demonstrates use of <pre><code>, <pre><samp> and <code>, though not just <samp> or <pre>. (I use bare <pre> elsewhere on my site, but haven’t had cause to use bare <samp> yet.) What can I say? I’m a snob. Also there are subtle differences in style between the two. (I have <samp> be truly monospaced, beca