3 ms·
On that note, why don't our browsers render Markdown natively? Without extension. Just pick a markdown renderer and say 'screw you' to everyone else. I would s
by busterarm 11y ago
On that note, why don't our browsers render Markdown natively? Without extension. Just pick a markdown renderer and say 'screw you' to everyone else.
I would serve up all of my static content as Markdown _tomorrow_ if that happened.
- dredmorbius 11y agoWell, there's a markup language aimed at hypertext documents, oddly enough. It's called hyper text markup language.... Markdown is a good start at an authoring lanaguage, and it's lightweight. It's not complete of itself, though. I'd actually lean strongly toward LaTeX. What ePub does is to take HTML and reduce it to a decent set. Ultimately, I think that it, or some alternate set of basic document templates are pretty much what we want: 1. Index / landing page. Essentially a directory. 2. Article page. 3. Gallery page. A set of thumbnails or other items displayed, many to a page (10, 25, 100, 1,000, ...). 4. Discussion. That's ye olde threaded / flat set of comments on some topic, with or without an article. Possibly a few other bits. Anyone who's worked with a reasonably robust CMS (Wordpress, Drupal, Mediawiki, etc.) probably has a pretty good sense of what these might be. The real challenge is that there's nobody to whack you upside the head for posting utterly gobshite HTML on your own site. This is a place where, as much as I dislike major search engines laying down the law, I'd like them to do so. Strongly encourage well-formed Web sites and pages, and, especially, to provide a bonus for high-reputation authorship, which would require both metadata (author field) and if possible, support for signing major payload (textual content, individual images or multimedia if possible). Perhaps a few other bits....
- busterarm 11y agoI mostly agree about HTML but it gives people too much rope to hang themselves. Like you pointed out, it's also too easy to write bad HTML. Not so much with Markdown.
- dredmorbius 11y agoPeople will write shitty websites in straight-up 8-bit ASCII. If there's not some external authority running herd, they'll just do stupid stuff. All body text in bold. Or <h4>. Every last goddamned paragraph explicitly positioned. Yes. For real, some guy who writes interesting atmospheric physics stuff in ... Colorado or Utah. The colour choices. The animations. The autoplay audio / video. I could go on. Any tagging is sufficient rope. People are idiots. Either rank/placement tools which downgrade that, or a client which effectively does on-the-fly rewrites of the entire source, are pretty much what you need. Oh, and don't get me started on the clever types. You've seen fonts constructed entirely out of CSS, no?
- dredmorbius 11y agoAlso: bare-ass raw HTML5 is actually really, really good. It does a nice job of providing structural definition, and I strongly recommend Mark Pilgrim's Dive Into HTML5 as both a guide and demonstration (in its Web incarnation) of that ability. It still lacks a few things, which both hNews and ePub could extend, and a few other bits. 1. Metadata. Authorship, publication date, title, and some sort of content valididty really need to be a thing. hNews and ePub both go there. 2. Notes. I don't care how they're presented, but sidenotes, footnotes, endnotes, need to be integral to HTML. I've gussied up some solutions myself, they kinda-sorta work. I'm not entirely thrilled. These should be entirely browser-native and not require JS. 3. Some sort of hierarchical discussion. Comments, etc. Essentially a marriage of the browser and the Mutt or tin/rtin newsreaders. With filtering and other capacities. 4. Reputation management. Entirely local, or distributed. Good and bad authorship, as with elections, should have consequences. 5. Curation. Why this is lacking from current generations of Browser I don't know. Add to this an in-browser set of styles which can be applied to the document templates mentioned above, and we're getting somewhere.