absolutely against the elementary separation of concepts ... use the web server itself to serve dynamic content ... very efficient.
(I hope I didn't thereby garble.) It's not so much they're nonseparated, but separations being in source, where a nonprogrammer might not look. People rail against ``monolitic'' design/implementation, but if the code is modular (abstract libraries etc), it's fine. Ofcourse, nonprogrammers not can easily change it, but that might be OK for the goal e.g. business website (as you mentioned) not changing much not needs ``user''-modularity. Further, maybe see ``literate programming,'' which keeping concepts separated, but implementation integrated. (Idea is write fully description for programmers, users,, (intelligent (or not-so) agents to whom germane) interjected with computer instructions formate to compile) Doing rightly, even smallers benefit, less resource and less maintainence/inscrutibility.