5 ms·
One thing CMSes have that SSGs don’t is: the ability to create posts without editing the source. Simply login to your admin panel and start writing. No Git repo
by colejohnson66 4y ago
One thing CMSes have that SSGs don’t is: the ability to create posts without editing the source. Simply login to your admin panel and start writing. No Git repository or build scripts required.
- replygirl 4y agoi've found that folks without git experience are fine to use github.com as a cms when you take 20 minutes to show them how to edit, submit as a pr, and check the preview deployment before merging
- marcosdumay 4y agoYep. There is a long line of people complaining that git is hard to learn on the internet. But I've never met anybody on the real world that had any problem with the basic cycle of edit - push - review - accept (or the even simpler edit - push).
- andi999 4y agoYou can directly push after edit? No add, no commit?
- marcosdumay 4y agoSome software join it all in one step. Like the GitHub GUI the GP is talking about.
- anamexis 4y agoThere are some really nice tools out there that bridge that gap, like Forestry: https://forestry.io https://forestry.io
- throwaway0x7E6 4y agoCMS/WYSIWYG functionality does not necessarily have to be baked into the application that serves the content
- zinekeller 4y agoCMSes and SSGs aren't necessarily mutually exclusive: WordPress can be an SSG. The only thing about SSGs are they don't static webpages for serving but the process of creating it doesn't matter, whether it's handcrafted (MarkDown) or integrated into a CMS.