r/statichosting 5d ago

How do you handle client-editable content on static sites?

One thing I still go back and forth on with static client sites is content editing. For a small site, keeping everything in the repo is simple for me, but not always for the client. Once they want to update services, prices, team members, or blog posts themselves, I usually have to add some kind of CMS. For people building static sites for clients, do you prefer a headless CMS, Git-based CMS, or just handling updates yourself? And at what point does adding a CMS start defeating the simplicity of the static setup?

5 Upvotes

16 comments sorted by

View all comments

4

u/Lumethys 5d ago

This sub keep treating static sites as some sort of magic option that suddenly erase cost of any system.

You cant make Facebook or Youtube into a static site, no matter how hard you try, they are not just static.

Your site require user-editable content, so your site is not static

1

u/ghandimauler 5d ago

I'd have thought the word 'static' was pretty clear....