My blog is built using a static site generator (currently Gatsby but I've been through some others too) and I never had any issues with that. Of course, something that works in my case may not work in yours. I am happy with opening my editor, pulling my repo and committing every time I want to write/edit a post. In fact though, If I was an editor in a blog for profit, I would probably have more important things to do than messing with Git. That's a case where a static site generator wouldn't be helpful.
Static site generators (or the JAMSTACK if you will) have come a long way and now there are Headless CMS APIs you can use to make it kind of dynamic, there are admin GUIs that you can attach to your blog to use locally (both self-hosted and online). These though would come in a cost, wheather is paying real money to host or paying with your time to maintain and set up the infrastructure.
I would say write down the capabilities you want to have and what your end goal is. Then decide based on these.
Unfortunately, there is no great answer, hope that was helpful.
Dheyson Alves is a software engineer, front-end focused with 4 years of experience in the industry. Offering expertise in developing dynamic learning experiences for web and app-based audiences.
My blog is built using a static site generator (currently Gatsby but I've been through some others too) and I never had any issues with that. Of course, something that works in my case may not work in yours. I am happy with opening my editor, pulling my repo and committing every time I want to write/edit a post. In fact though, If I was an editor in a blog for profit, I would probably have more important things to do than messing with Git. That's a case where a static site generator wouldn't be helpful.
Static site generators (or the JAMSTACK if you will) have come a long way and now there are Headless CMS APIs you can use to make it kind of dynamic, there are admin GUIs that you can attach to your blog to use locally (both self-hosted and online). These though would come in a cost, wheather is paying real money to host or paying with your time to maintain and set up the infrastructure.
I would say write down the capabilities you want to have and what your end goal is. Then decide based on these.
Unfortunately, there is no great answer, hope that was helpful.
Thank you, it was helpful!