I have used MODx CMS for a couple of sites, and it has worked really well. You can allow both frontend and back end editing, creating, etc of pages, blogs, you name it. It is still fairly new, but I have been impressed with the support and capabilities that it offers.
I also use Wordpress for smaller sites that are more basic, such as a few "static" pages, and use the "blog" functionality for updates, newsletters, etc. Works pretty well and is fairly easy to learn for a basic computer novice. ---- [email protected] wrote: > ********************************************************************* > WEB STANDARDS GROUP CMS MAIL LIST DIGEST > ********************************************************************* > > Due to an upgrade of SmarterMail, digests seem to have had a problem. > > We are working on it. > > ********************************************************************* > From: James Gollan <[EMAIL PROTECTED]> > Date: Wed, 11 Jul 2007 10:06:20 +1000 > Subject: Re: [WSG CMS] RE: WSG CMS Digest > > 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: > > > > > > > From: "Raena Jackson Armitage" <[EMAIL PROTECTED]> > Date: Wed, 11 Jul 2007 10:11:02 +1000 > Subject: Re: [WSG CMS] Client - Site Edits > > Hi Kevin, > > On 7/11/07, Kevin Ross <[EMAIL PROTECTED]> wrote: > > > > The site is not extremely complex, but is more than a little task for > > someone who does not design web sites. > > > > I am wondering for advice on this situation and I am also wondering how > > others handle ongoing updates after the initial design has been implemented. > > > > I am also wondering if a CMS system would, in any way, be a solution to a > > situation like this. > > > > You could try using a tool like WordPress that has support for static pages > -- she could just avoid the whole blog bit altogether (or use it for a > "what's new" type section). It might mean a bit of a learning curve on your > end, but once it's there you can just let her go for it. it's easy to > upgrade too. I've done this before and it worked reasonably well. > > > -- > Raena Jackson Armitage > www.raena.net > > > ************************************************************** > Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ************************************************************** > > ************************************************************** Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] **************************************************************
