3 ms·
Really? The above HTML will look very readable if you just fire it up in a web browser. And if we all agreed on the location of an optional CSS file (e.g. ~/.de
by dheera 10y ago
Really? The above HTML will look very readable if you just fire it up in a web browser. And if we all agreed on the location of an optional CSS file (e.g. ~/.default.css) anyone would be able to customize how all their documentation looks. It would be totally optional and just make semantically-good HTML go from readable to super-pretty per-user custom themes. Totally optional -- if you don't have it, you'll still have something extremely readable, well more readable than Markdown.
<html>
<head>
<link rel="stylesheet" href="~/.default.css">
</head>
... your documentation goes here ...
</html>
The best part? If you don't think <i>this</i> is readable, just double-click and open the thing in a plain-old web browser and it'll be more readable than Markdown.
- accordionclown 10y agoyou have a point. but you're just talking about _reading_... when it comes to typing, and especially _editing,_ all that markup cruft becomes a distraction (at best), and usually much more like an irritating obstacle. and you glossed over the ’ which needs to sit in the middle of every contraction. like this: “if you don’t have it, you’ll still have something...” ick. no thank you.
- dheera 10y ago"if you don't have it, you'll still have something ..." is perfectly fine in HTML. If you for whatever reason believe left and right quotes should make a difference, “if you don’t have it, you’ll still have something ...” will be fine in HTML as well. You don't need awful escape sequences for these. Browsers will render them just fine.