11–20 of 41 posts
However, in hindsight it sucks... all that documentation is so much harder to read in things like githublab... Those things render .md files just great, however, all these old docs look like html and require JS to render...
Just write pure markdown in .md files... view them w/ tooling, don't build tooling into the file...
I like this, but I hate the FOUT that it seems to create
Off topic but I never knew the term for this. The cbcnews.ca site got rebuilt in react recently and the result has this one bug where when loading, some headlines flash an entirely different but also valid headline for the same story for a split second. When it comes to news, a FOUT like that makes me rather paranoid about maybe I'm getting a tailored headline for my demographic.
I wouldn't put it past the major publishers to have moved beyond A/B testing for an overall headline winner to more segmented optimization based on tying A/B performance to first and third party data they have available on you, and further optimizing their headlines to reflect whatever performed well for traffic like you, rather than just performed best overall for all traffic.
1. https://contently.com/strategist/2015/02/04/how-buzzfeed-r29...
I like this, but I hate the FOUT that it seems to create
Off topic but I never knew the term for this. The cbcnews.ca site got rebuilt in react recently and the result has this one bug where when loading, some headlines flash an entirely different but also valid headline for the same story for a split second. When it comes to news, a FOUT like that makes me rather paranoid about maybe I'm getting a tailored headline for my demographic.
I don't think a belief is paranoid when it's both rational and evidence based.
Please don't make websites require JavaScript to display simple text.
The PolymerElement project's has offered declarative client-side Markdown for years:
# Hello
For math, you can do a similar thing with Katex: https://github.com/justinfagnani/katex-elements
c = \pm\sqrt{a^2 + b^2}On my browser, this page flashes raw HTML before it displays the rendered page - not a nice experience. I don't like the idea of this at all, anyway - surely it's better to render content once rather than render it thousands or even millions of times clientside?
If you can serve static HTML, why not just do that?
How is this remotely elegant? You're including a script to render simple formatted text, something that can be accomplished by statically compiling from markdown to HTML before serving. If you can serve static HTML, why not just do that?
I'd definitely call it elegant, though not exactly minimal.
I helped run a fraternity website for a bit. If I could say, hey just download the source from chrome, tweak the bulletin in notepad, and upload it back to the ftp page that would have been great.
It also has the text in readable markdown. If you browse without JS it still works!