3 ms·
Which uses one of the most complicated static site generators out there... as in a blog which was valid one day wouldn't "compile" the next. It's just bloody ma
by falcolas 8y ago
Which uses one of the most complicated static site generators out there... as in a blog which was valid one day wouldn't "compile" the next. It's just bloody markdown; how unnecessarily complicated is a system that can't compile markdown from one release to the next?
- thoughtspile 8y agoWhy no, github-pages does not enforce Jekyll! You can just put a bunch of HTML there. I use hexo, which I like. I could also write HTML by hand or generate directly from markdown. The default Jekyll setup does indeed rely on some implicit theming, which is not very convenient.
- falcolas 8y agoWhich has nothing to do with how terrible their static site generation tooling is. "You can bypass it" isn't a convincing argument that it's any good.
- thoughtspile 8y agoI wouldn't even call it a bypass — it's there as a safety net for people who just dump a bunch of markdowns into the repo and expect it to work somehow — it does work somehow.
- lloeki 8y ago> You can just put a bunch of HTML there If I were to already have the artifact files locally I wouldn't commit them in git and push to GitHub, I'd upload them straight to S3/Neocities/whatever. The whole point of Pages is to push some source material and have some CI/CD do the build and deploy.