4 ms·
> SSGs with plain text files are brilliant once you are set up, but it's a big hurdle getting there. Even in that case, not nearly as practical, unless you mos
by FalconSensei 4y ago
> SSGs with plain text files are brilliant once you are set up, but it's a big hurdle getting there.
Even in that case, not nearly as practical, unless you mostly do long-form and only post from your computer. Even with SSG set up, having to be on the computer to create a draft, or make a quick correction, is really a bother.
Also, when you own everything, you end up spending more time tinkering with it, which is not bad per se if you are having fun, but terrible if your goal is to actually post. Those 2 things - harder to post and easier to get sidetracked - explains why so many SSG'd blogs are made up of a few posts explaining why and how it was set up, and maybe a couple actual posts.
- NateEag 4y ago> Even with SSG set up, having to be on the computer to create a draft, or make a quick correction, is really a bother. I think you might be able to solve this with Syncthing and a watch process on your syncthing server. Commit and render on each change, and optionally sync if the rendered site is different from the previous version. ...granted, that's a really tech-nerd setup.
- yjftsjthsd-h 4y agoHow is running syncthing better than git or the site generator?
- NateEag 4y agoSorry, I was really vague there. If you run syncthing on your mobile device, you could make edits to a local copy of your plain-text content, and have those edits auto-committed/rendered/synced when they hit a computer housing the actual git repo. I personally despise typing on my smartphone because I'm so much slower on it and I'm much more error-prone this way, but I use something like this for managing my personal todo.txt file and it works pretty well.
- Gigachad 4y agoAt that point you may as well use a real cms.
- NateEag 4y agoI dunno. I have basically this working with my todo.txt file between my laptop and phone, and it's incredibly low-maintenance. Most CMSes mean running a complex app, a full DB engine, and having to stay on top of security updates for all that. Heaven help you if you run a CMS with a bunch of third-party extensions. For my static sites I have SSH and nginx. Nothing else needed. Static isn't always the answer, but where it does fit it's hard to beat for simplicity and efficiency.
- benoliver999 4y agoThat's what stuff like Netlify does. You just set up a git hook to build the site when you push, and it all happens automatically.