Hacker News new | ask | show | jobs
by asadjb 2828 days ago
Because in my (somewhat limited) experience with CMSs' the definition of the data in separate from the layout, which makes sense if you're building a larger site where separation of view and data makes maintenance easier.

However, if all you're doing is building a 5 page website, it's much simpler to just put in the configurable parts in the HTML as you're building it and let Vapid handle the dashboard, which the client can easily use to make small changes as needed.

2 comments

Honestly, if all you're building is a 5 page website its simpler to bundle infrequent content updates into a maintenance retainer with the client. In my experience there's no such thing as a simple CMS, its either small enough that you can handle it via email, or complex enough to need something larger.
> However, if all you're doing is building a 5 page website,

Why not cut to the chase and show the client how to use FTP and a text editor? Why add more complexity beyond that?

For likely the same reason a cleaning service doesn't offer to show the customer what chemical mixture to use to clean an especially grimy tub or oven. The customer is paying for the convenience, not a tutorial, and the cleaners aren't in the "teach a man/woman to fish" business.
Because sometime clients; especially extremely non-technical one, are scared of anything that looks like code. HTML definitely looks like code. :)