A good CMS will keep the content and the presentation quite distinct.
This makes it quite easy to develop the underlying system and logic and
then run it through a theme system. The theme system is where the
individual pieces of content are wrapped in your sites HTML structure.
The upshot of all of this is that you should be able to take a static
site design and apply it to a CMS driven site so that is is basically
invisible to the end user.
My personal preference for developing these sites is Drupal. This is a
bit of overkill for a very basic dynamic site, so the suggestion of
Wordpress or even Textpattern may be worth considering.
There will be a learning curve involved, and the first time you
implement a site using a CMS it will take a lot longer than you had
planned. But it really is upskilling for future sites, and it allows
you to offer a lot more to your client (and also charge for a more
comprehensive service). Perhaps looking for a developer who you could
work with on the more complex projects would be worthwhile if you don't
want to take on the code straight away. You can separate the front end
and back end development fairly efficiently if you have good
planning/communication.
On 11/07/2007, at 9:34 AM, Kevin Ross wrote:
**************************************************************
Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
**************************************************************
