My advice to OP would be to not fall into the trap of the latest shiny object. Gatsby/Hugo + Netlify is definitely an awesome setup for something like a portfolio or a brochure site that doesn't get updated frequently. Continuous deployment from Git to Netlify is a dream.
HOWEVER, for an editorial site being updated daily, having a workflow where you can update via logging into a CMS with robust SEO features is going to be far more important. Netlify CMS (which you can attach to Hugo, etc) is just okay, and doesn't offer enough features out of the box.
If I was OP I'd go flat file CMS like Statamic or Kirby, or if you're not well versed in front-end development, gasp Wordpress. Wordpress, while bloated and generally terrible to work with, has plugins to handle every possible scenario an editorial site will encounter. Setting it up at first will suck, but the writing experience will be a much faster workflow.
Your last point is very important.
My advice to OP would be to not fall into the trap of the latest shiny object. Gatsby/Hugo + Netlify is definitely an awesome setup for something like a portfolio or a brochure site that doesn't get updated frequently. Continuous deployment from Git to Netlify is a dream.
HOWEVER, for an editorial site being updated daily, having a workflow where you can update via logging into a CMS with robust SEO features is going to be far more important. Netlify CMS (which you can attach to Hugo, etc) is just okay, and doesn't offer enough features out of the box.
If I was OP I'd go flat file CMS like Statamic or Kirby, or if you're not well versed in front-end development, gasp Wordpress. Wordpress, while bloated and generally terrible to work with, has plugins to handle every possible scenario an editorial site will encounter. Setting it up at first will suck, but the writing experience will be a much faster workflow.