If you're trying to shield the client from the code, it should work. My opinion is reserved for 1) A target client profile 2) An outlined objective for the CMS
Otherwise we're not talking about
content management strategy ...we're talking about a play pen to keep the client from hurting themselves.
These things merely set up an online version of notepad, not a CMS. At best it's a neat way of
managing the layout ...and shielding the developer from thinking about client content.
CMS installs were never about a "don't ask, don't tell" firewall between client and developer. I usually roll my eyes whenever the discussion turns to "the best" CMS without any mention of the client or objectives. Because there is an obscenely high probability the thread will have the least to do with either content or reaching an objective.
And no, I don't consider the color scheme and client okay of generic stock photography a content management strategy.
My opinion is these are anti-content-management applets. If anyone ever talks about content driven website design and one of these in the same paragraph, it'll be a surprise to me.