3 ms·
> That's just client side templating. Which has the same problem they all do of being greeted with a white page until ALL the content is ready. Or being greete
by masklinn 10y ago
> That's just client side templating. Which has the same problem they all do of being greeted with a white page until ALL the content is ready.
Or being greeted with a white page period if you're using a non-JS enabled HTML client (noscript, CLI browser).
- coldtea 10y agoIt's 2016, if you use a non-JS enabled HTML client you better be used to the breakage.
- laurent123456 10y agoIn this particular case, wouldn't they see the plain text markdown? (which in many case is just as good the html)
- masklinn 10y agoKinda, it looks like they add a bit of CSS (basically make everything monospaced & pre) so the Markdown text is visible when JS is disabled (noscript), but in a CSS-less browser (e.g. links) the file is received as HTML, and the Markdown code is directly interpreted as HTML, which makes for an unreadable mess (the whole thing is a single "line" with newlines collapsed to spaces) You're really better off using a static conversion tool, or using markdeep as a static conversion tool (with ?export)