7 ms·

It's a pretty common blogging method. Google and many other orgs do that too.

• notretarded 6y ago
  Thank you for your contribution
• breck 6y ago
  Is it? Can you provide some links to examples?
  • jspotanski 6y ago
    Microsoft does it: https://docs.microsoft.com/en-us/windows/wsl/install-win10 https://docs.microsoft.com/en-us/windows/wsl/install-win10
    • judge2020 6y ago
      for reference: https://github.com/MicrosoftDocs/wsl/blob/master/WSL/install-win10.md https://github.com/MicrosoftDocs/wsl/blob/master/WSL/install...
  • qbasic_forever 6y ago
    Dive into the JAMstack and file-based CMS world. Netlify is kinda the big name here: https://www.netlify.com/ https://www.netlify.com/ Push markdown content to git -> Netlify builds using your file-based CMS of choice -> HTML published as blog, etc.
  • mr_toad 6y ago
    Static site generators have been around for ages. Jekyll was one of the first, as far as I know, but there are dozens of others now. https://jekyllrb.com/ https://jekyllrb.com/ https://jamstack.org/ https://jamstack.org/
    • motogpjimbo 6y ago
      I assume you mean NodeJS-based generators? Static site generators as a concept have existed since the very earliest days of the web. I worked on a team that used an in-house SSG to maintain dozens of sites years before NodeJS (or even V8) existed.
      • mr_toad 6y ago
        Jekyll uses Ruby, not node. I don’t know what all the others use, there are so many. Sure, generating HTML via another language is not new, but SSG pushed back against the notion of using dynamic CMS systems (which were de rigueur in the early 2000’s) in favour of static pages hosted on serverless systems and like GitHub pages and S3, with content (mostly markdown) held in version control systems instead of a database.
  • jefftk 6y ago
    Here's one: https://amp.dev/documentation/examples/components/amp-analytics https://amp.dev/documentation/examples/components/amp-analyt..., backed by https://github.com/ampproject/amp.dev/blob/future/examples/source/1.components/amp-analytics/index.html https://github.com/ampproject/amp.dev/blob/future/examples/s...
  • eyelidlessness 6y ago
    It is! Beware the lure of MDX/equivalents. If you want to provide structure to your content and maintain it colocated to where you use it (or imported and type checked for where you have that kind of reusability), components in Markdown is an awful experience. Inverting that and writing Markdown within posts is my current solution. It’s not as nice as a plain .md file but it lets me mix writing and structure without compromise
    • eyelidlessness 6y ago
      Realizing I should add a little more context: it’s very common to use Markdown for content and even for generating routes or subpages. But when those pages/posts/sections are expected to provide a certain data/content structure it’s generally provided by “front matter” metadata or mixed-source data like MDX which mixes JS/TS and JSX into Markdown. That experience doesn’t have any real editor safeguards, though it has some linting tools. But it has basically no dependency checks on what would be rendered. You just have to cross your fingers and hope. And if your content is expected to have any particular metadata, good luck refactoring.
  • fctorial 6y ago
    Can't list many from the top of my head. I've seen 'edit source' links on a bunch of sites.