this post was submitted on 13 Feb 2024
211 points (97.3% liked)
Programming
17432 readers
104 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I love simple sites, but I feel that there's something to be said for design philosophy vs tooling.
Take vanilla WordPress for example. I find it relatively easy to manage static content, especially when running it in a container to categorically prevent dependency concerns. Is it overkill for a simple site? Perhaps, but does it work and is it easy to use? It's possible to use these tools to manage a mostly static, text based, minimal to no script website. The key is recognizing the value of that simplicity and providing that simple to read, simple to use experience without distractions.
WordPress will never be as simple and performant as a truly static site, but we can do a lot to cut down the cognitive load, and we should.
If you want the ease and functionality of WordPress, but you plan to have a relatively simple site, there are other CMS options that are lighter weight and easier to work with. I've used GetSimple for years with some of my sites, it's much more performant and easier to maintain. And the non-technical folks that manage content actually found it easier to use than WordPress.