What is this aggression about not wanting a CMS? I have found the examples you quote to be true of CMS's also. I can assist myself to some extent, but support I expect from the original developer. If they don't provide support, I won't use them.
CMS are built around end users so they come with document maintenance etc. Think of wordpress - you add a blog post, add a page, you can edit them (it keeps versions), you can have taxonomy included for free. The theming just "works" (in general). You can have comments with plugins that allow you control how it all fits together. SEO? Done... no follow links? Done.. want to change your menu? Drag and Drop... Want a backup? Plugin... Want to include Google maps? Want to integrate maps with your database? Need multiple levels of user access? Want friendly URLS? Want a calendar?
All these things come with a CMS. All these things come tested and configured.
A decent developer will even add custom admin pages and multiple user levels- want to upload a new file? change your source data?
Without a CMS you're relying on someone to handle all of these things. A framework gets you half way there. It forces the developer to follow standards in how to implement your site. It enforces MVC model, it forces adherence to APIs, it gives you libraries and plugins.
Not all CMS are created equally.
If you have a fairly simple site requirement then someone will develop that site and provide you "admin" pages and do that from scratch (a lot of the domain management tools that domainers sell are done this way... but it's time consuming). A lot depends on the relative complexity of your requirements.
I would think something like Drupal would do what you want out of the box but it's complex to get right and overkill when simplicity is needed... Wordpress / Joomla is similar in that it's able to do a lot and get it right quite simply but it gets killed by complexity. (imho)
Theming and designing the templates should be done by someone who can theme properly. In something like Wordpress lots of themes "work". Other cms you will have less success as it just doesn't have the same community focus. CMS will output using a template engine. Frameworks will work with template engines.. custom web dev? it's up to the developer.
Think of it like cooking a pizza:
Bespoke development - get flour, eggs, yeast, tomatoes, milk...make dough, make sauce, ....
Framework - get dough, get sauce, add cheese, construct
CMS - get premade pizza from store
Then say you want to add pepperoni:
Bespoke - find pepperoni, slice pepperoni, move ingredients to find room for pepperoni and add and bake
Framework - move ingredients around to find room, add pepperoni
CMS - tell them to add pepperoni
Something like that
Frameworks are targeting custom sites or developers who would white label their own product or have continual support lifecycles. CMS are better for delivering and turning over a site - and they exist at all levels (simple, complex).
This will be my last post on here because I have other things to do and these are all questions/comments you should get from othes and a lot of this opinion and opinions are like a$$holes.....
