in-page editing
Posted: Fri Nov 09, 2012 10:40 pm
I just noticed a comment on the CMS Critic site (go vote for CMSms) about in-page editing for CMSms.
Does anyone actually like in-page editing?
I was talked into using Drupal for a few projects by an over zealous developer of mine and I regret every minute of it. Mostly because of the mix of back and front end editing.
I develop sites with a very heavy focus on client usability. The drupal sites we did have a much heavier support cost to me because clients find it confusing and hard to use. They argue that I cannot charge for support if I didn't educate them properly in the first place. I did, but I can see their point, it's just not end-user friendly.
This has never happened with CMSms - ever. We offer a half hour to one hour training for the person that will update the site (usually an admin person or family member of the client).
With just the CSMms permissions we manage to create an environment that a client quickly feels confident using, but at the same time, they can't screw it up. (Thankyou MicroTiny).
The key, though, is having one window with the admin open, and another window with the site open.
Drupal on the other hand is all over the place. In-page editing for page content, but backend editing for anything else. If you want to see what your changes look like without the editing toolbars - you have to open another browser for that. Most clients don't have a second browser. Not a client friendly work flow.
Sorry, this is a bit of a rant - but CMSms doesn't need in-page editing. In my opinion, if configured correctly, CMSms is the most intuitive CMS out there for end users - the clients that use it every day.
Simon66
Does anyone actually like in-page editing?
I was talked into using Drupal for a few projects by an over zealous developer of mine and I regret every minute of it. Mostly because of the mix of back and front end editing.
I develop sites with a very heavy focus on client usability. The drupal sites we did have a much heavier support cost to me because clients find it confusing and hard to use. They argue that I cannot charge for support if I didn't educate them properly in the first place. I did, but I can see their point, it's just not end-user friendly.
This has never happened with CMSms - ever. We offer a half hour to one hour training for the person that will update the site (usually an admin person or family member of the client).
With just the CSMms permissions we manage to create an environment that a client quickly feels confident using, but at the same time, they can't screw it up. (Thankyou MicroTiny).
The key, though, is having one window with the admin open, and another window with the site open.
Drupal on the other hand is all over the place. In-page editing for page content, but backend editing for anything else. If you want to see what your changes look like without the editing toolbars - you have to open another browser for that. Most clients don't have a second browser. Not a client friendly work flow.
Sorry, this is a bit of a rant - but CMSms doesn't need in-page editing. In my opinion, if configured correctly, CMSms is the most intuitive CMS out there for end users - the clients that use it every day.
Simon66