Rather, The page includes the Markdown of the article, which is then rendered to HTML in client-side JavaScript, after page load. This is not a good approach: it means that everyone will always get a complete rerender after the page finishes “loading”, as it switches from monospaced Markdown to the final HTML. Doing it before the load event would be a little better, as it could make it so that many people wouldn’t get the flash of Markdown source, but the real solution is to please render the Markdown on the server and serve real HTML instead of <pre>[Markdown]</pre>.