DEV Community

Discussion on: What non-CMS tools would you use to make a small but growing website?

Collapse
 
phlash profile image
Phil Ashby • Edited

I had similar needs of my own, and chose:

  • Hugo for site generation
  • Content managed in Github (private repo)
  • VScode for manual editing of markdown and configs
  • Self-hosted, because I already did that and like to own stuff (also pain!)
  • Github webhook to trigger redeploys
  • Netlify CMS to provide a nice GUI, avoiding the details of gitflow for most things and not imposing it's own ideas on content structure / format (I have less-technical friends)
  • netlify-cms-oauth-provider-go to connect my self-hosted site to Github without sending credentials to Netlify, although I needed a couple of fixes.

Current test site phil.ashbysoft.com/hugo-test/

Collapse
 
tdbaylis profile image
Td Baylis

Speaking of Netlify, I was gonna ask: how about combining headless with WordPress? I stumbled upon this article on Netlify benchmarking a WP site pre/post-headless switch and the results are pretty impressive.

Netlify WP headless CMS article

Have you thought about a headless multisite (not sure if you are planning on servicing different companies, but this could add merit to something like WP if you go the headless route)?

Collapse
 
drmikecrowe profile image
drmikecrowe

One of the downsides with headless WordPress is where you host WordPress so you can access the posts via API. I've looked at Gatsby + WordPress, and it's pretty slick. However, a free WordPress.com account doesn't let you get the posts via API as best I can tell. I suppose you could run it locally, though

Collapse
 
monicat profile image
Monica Macomber

Someone else suggested a headless CMS too, I am considering it now 👍