This is... at best not favorable for a lot of static blogs.<p>For people who didn't understand what this is doing - it's using client-side JS to load the markdown files from GitHub, compiling it to HTML and displaying it on the browser.<p>Looks like the advantage of this is that it's a one-time setup - you don't need to build the files every time you commit, you can add your markdown files on GitHub and it automatically gets 'added' to your blog.<p>The downside of this is that this makes RSS feeds impossible, and non-JS users will suffer.
I do this for automatically generating pages on my personal website for various projects via Jekyll.<p>So <a href="https://captnemo.in/ideas/" rel="nofollow">https://captnemo.in/ideas/</a> loads the README from <a href="https://github.com/captn3m0/ideas" rel="nofollow">https://github.com/captn3m0/ideas</a>.<p>If you'd like to replicate, use this layout[0], and create a post with just a few bits of frontmatter[1]<p>The obvious advantage is that I can now serve READMEs for various projects within my website, without having to worry about updating it in any way. The READMEs stay in their respective projects. Its all done client side though, so not recommended if you'd like to use the page on your website as the primary. The one issue is that internal links in markdown don't work easily.<p>[0]: <a href="https://github.com/captn3m0/captn3m0.github.com/blob/master/_layouts/repo.html" rel="nofollow">https://github.com/captn3m0/captn3m0.github.com/blob/master/...</a><p>[1]: <a href="https://github.com/captn3m0/captn3m0.github.com/blob/master/projects/ideas.md" rel="nofollow">https://github.com/captn3m0/captn3m0.github.com/blob/master/...</a>
I have created something similar. I have a content folder with articles and auto generate content on my site at each commit. I built it as a Docker container and I run it on Nomad. It’s interesting how much content (crm?) we can put together by scraping other apps we use (github, hacker news, reddit, etc)