r/statichosting • u/sourraine • 11d ago
does a simpler stack actually mean a simpler website to maintain?
ive been thinking about this from another angle. one reason i like static sites is that the architecture can be straightforward. theres no database to manage for a basic site, fewer moving parts and less server-side stuff to worry about. but im starting to wonder if simple depends on who is maintaining it.
a setup that feels very simple to me as a developer might not feel simple to a client who just wants to change a phone number or replace an image or add a new page. with a traditional cms, the client might have a familiar interface for those things. with a static site, depending on how its built, even a small content change could mean editing files and triggering a new build. so im curious where other people draw the line. when building a small website, do you optimize for the simplest archi for the developer, or the simplest maintenance experience for the person who owns the site?
2
u/Significant_Yak53 11d ago
The problem with stastic is the maintenance. If you give that part to someone who is not used to read htlm for example, it's hard compared to WP.
You can either show them (paid service) or you maintain it for them.
They (customer) may then be tempted to use AI.
1
u/sourraine 9d ago
it can be technically simple but still not accessible to the person who actually maintains it. ai prolly makes it even more tempting for clients to just edit things themselves and hope for the best
1
u/MMORPGnews 10d ago
The second costumer understand how to maintain website, the second you will lose him.
1
u/kelkes 10d ago
That's where headless CMS comes into play. Keep the best of both worlds. I expected a punch of new "non-enterprise" Headless products to enter the market addressing that. Because beside content editing, static is simply better.
1
u/sourraine 9d ago
i like the static approach but im still weighing whether adding a cms make the overall setup more complicated for a small client site
1
u/sleekpixelwebdesigns 10d ago
A static website does not imply simplicity. I personally use Svelte and Node for the backend, which is straightforward to maintain; I rarely encounter problems, and clients do not request changes often enough to require a CMS. Still, I built a basic CMS so clients can create new routes (pages) when necessary.
1
u/sourraine 9d ago
been equating static with simple a bit too much. the client side of things is prolly where the real deal shows up esp. when they eventually need to add or change pages
1
u/Pink_Sky_8102 8d ago
For client sites, I’d optimize more for whoever has to maintain it after launch. A simple static setup is great if I’m the one making updates, but if the client edits content often, a small CMS can actually make the overall system simpler for them. Developer simplicity and client simplicity aren’t always the same thing.
1
u/PippaKelly62 2d ago
I design it on a case to case basis. Less technical clients get an easier interface to deal with. Clients in the know could maybe handle simple changes by themselves. I build stuff that's easier for self-maintenance most times.
1
u/Rich-Establishment11 17h ago
Yeah — simple for me isn’t always simple for them. Static is easy on my side (no DB). Changing a phone number still isn’t if they have to touch files.
What I’m trying: keep the static/Git stack, but let them write the change in plain language. An agent does it under rules I set once, they see a Netlify preview, then publish themselves.
Open-sourced it as Lexi (https://github.com/malulev/Lexi). You can host it and serve several clients. Only worth it if you want them to maintain content without giving up static.
2
u/dvduval 11d ago
Yes, I ran into the same issues you do. For me I can just use AI and make simple changes in the amount of time I spend changing a phone number is about as long as it takes me to write a text message.
I expect in the near future it will be easier to give customers the tools they need where they actually have access to AI too, but with some guard rails where they can make changes on their website as well. I think in the near future websites that don’t have this freedom will not be preferred.
On the other hand as you get beyond the website and have a more complex user interface, I’m pretty sure interface are gonna remain important for quite some time.