Skip Navigation

Is a static site generator suitable for my project?

Hi! I've been working with Hugo for a while and I also created a free MIT licensed theme with it!. I love the flexibility and the ease of use.

But I'll have to wok on a bit more complicated project than a simple showcase website/blog. The content to be published on it is not a lot, but it would be definitely better if I could:

  • Get/Post some content with API to avoid posting multiple times the same articles on different platforms, getting modifications as well.
  • Send posts digests via email / Download PDF post digests.
  • Post on social medias (?)
  • Parse some content from CSV files / I don't know anything about databases.

Now I know that I can do something like this with a little systemd service I might write on my own and something like Zapier + RSS feed + Mailchimp. Also I could leverage Hugo modules and the .GetRemote / transform.unmarshal command, to get content from remote sources.

Now I'm not really a lot more than an amateur developer, I was thinking a headless CMS could pheraps do this stuff and more in a better way (?). I'm not a webdev and I know only really really basic JavaScript, I can use Bootstrap for frontend confidently and add SCSS to it. I know a bit of Rust too.

Would it be worth to take the time learning how headless CMS's work? I don't really want to go back managing Wordpress plugins, updates ecc.

Do you think I'm going out of a static site generator purpose with this kind of project?

1 comments