Plug-and-play inline editing for various CMSs would be nice. If this had more features, I could see using it with a structured, lightweight CMS like Perch [1] to edit structured content inline with the published pages.
At work, I'm supposed to change a lot of our existing websites over to "Wordpress CMS" because it'll make it easier for the admin staff to modify the website, for updates and such.
The problem is, they need to locate the login then they need to remember their account info, then they need to find the right page they want to modify, then they have to do a bunch of other clicks to get what they want.
Unfortunately, this tends to go woosh right over a lot of heads, and therefore stuff simply doesn't get updated - they send the 'update' via email to IT.
The cool thing about this createjs thing, is that you design the website, you put up the content and you have a simple login form. Everything is editable by clicking and typing directly from the site you're looking at.
I'm sure it'll help in situations like mine, for sure.
Some staff and volunteers pick it up quite easily, if they haven't already seen or used it before, but several people just don't do it, and instead I get a phone call or email saying "can you put this on the website?".
Incidentally, do you find a lot of people simply can't be arsed? One of our presenters (we're a radio station) is tech-savvy, has an iPhone, a Macbook, uses Facebook daily and so on. She's also one of the worst offenders for emailing me stuff to put on the website. I wonder if some people just plead ignorance to avoid having to do it themselves...
Anyway, back to the topic at hand, it would be one less excuse if we went to a solution like this - where it's simply a case of navigating to the page, clicking a button and editing it.
I'm also tired of fixing Wordpress malware issues for friends and clients that host themselves...
we dont do inline editing, but on-site editing where you navigate to the page you want to update and click edit, we then highlight all dynamic content on the page and bring up the relevant form when clicked.
In our first prototypes we were playing around with inline editing, but ended up concluding that it causes more problems than it solves when you're dealing with a real website with dynamic content.
One example: you have a news section, and on the homepage the last 3 stories are pulled in, but with the body text truncated to 100 characters since more would break the design. Inline editing here will be problematic. There are plenty of other cases (just think text-overflow: ellipsis;) and there's also the contextual problem of how to communicate to the end user that he is editing structured content that might be reused in different places on the site, with an interface that pretends to be completely WYSIWYG.
We think our way of on-site editing is the best compromise between making updates easy and making the conceptual model clear.
In this situation user would need to go to the article page to edit the actual contents.
Generally the promise of in-context editing is you can fix a typo from the same place you see it. I think trying to make it a pixel perfect "edit looks EXACTLY the same as view" deal is too literal.
http://concrete5.org is doing quite well with the overlay approach, and no one says our software isn't intuitive enough because the editor is in a window.
And http://www.deathmonkey.org/ was completely produced by sending emails from (old, pre-iPhone) smartphones on the road.
Aside from Hallo, Create also supports Aloha Editor (http://aloha-editor.org/)
We will have a hack weekend on Create in January in Zurich, and hopefully after that I'll update the demo setup with a lot more features enabled (formatting, images, workflows, etc)
What would also be awesome is a simple way to add options yourself via callbacks in JS.