Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Create - A new kind of web editing interface

createjs.org

Post reply on HN
Print view View original

21–30 of 73 posts

Re: Create - A new kind of web editing interface

#21

Post by sunahsuh »

lukeholder wrote: post #12

Please check out mercury editor. Much nicer and active development. http://jejacks0n.github.com/mercury/ other notable and far more advanced (over create): Aloha Editor http://www.aloha-editor.org/

From a cursory look: Mercury seems to be tied to Ruby and I'm not exactly enamored with the UI

Aloha uses jquery-based selectors to identify editable content areas as opposed to Create's more standardized and semantically accurate RDFa.

(This is based on all of 3 minutes of poking around so I don't claim complete accuracy.)

Re: Create - A new kind of web editing interface

#22

Post by Newgy »

veb wrote: post #8
asolove wrote: post #4

Inline editing is quite nice. I wonder if I am missing something about this: it seems to only offer italic/bold/underline/strike-through and no structural options? 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. [1] http://grabaperch.com/

Does it need structural options? 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 wh…

Same problem here. The admin site structure of the typical CMS is an abstraction that makes obvious sense to us developers, but not necessarily to the content managers. Inline is the future.

Re: Create - A new kind of web editing interface

#25

Post by Turing_Machine »

lukeholder wrote: post #12

Please check out mercury editor. Much nicer and active development. http://jejacks0n.github.com/mercury/ other notable and far more advanced (over create): Aloha Editor http://www.aloha-editor.org/

Thanks for all of these (and to the original poster, too). As it happens, I just started looking at editors for a mobile application.

Some instant thoughts:

Create seems to work fine on the iPad. Mercury sort of works, but kept switching out of edit mode for some reason. Aloha didn't seem to work at all.

As with some of the other commenters, I'm not wild about having the editor tied to a Rails backend (I didn't explore what kind of backend requirements Create has, though they seem to imply on the front page that it's at least somewhat portable).

The only other editor I've found that appears to work on the iPad out of the box is CKEditor. My old standby, TinyMCE, is supposed to support it, but I didn't have much luck (it may be that this isn't in the release yet -- I'll go back and explore the source tree later).

Granted, Apple has only had proper support for contenteditble on iOS for a couple of months, but I urge editor teams to please try to make their stuff work on the iPad. There's a huge unmet demand for that, and there's a first-mover advantage here. :-)

If they can do something clever with the UI to make the editor also usable on a device with a smaller screen (e.g. the iPhone), they'll really be cooking with gas.

Re: Create - A new kind of web editing interface

#28

Post by jsavimbi »

michaelbuckbee wrote: post #15
jsavimbi wrote: post #5

I've seen Thoughtbot do this with Copycopter ( https://copycopter.com/ ) as well as Plone and others. It's a great way to sell user-editing features to your clientele, but I would always start with actual copy prior to enabling it as real copy is just as important as functionality for product design. Yes, the marketing folks will just send you a bunch of disjointed word docs and expect you to assume that they'll fill…

I was really excited about Copycopter but found that their "search for the text you want to edit" interface was too confusing for my clients.

That's too bad. I too found Plone's in-page editing to be a little too far beyond the reach of the average client, but then again, I used to send static website "versions" of a website on zip disks to a client in the mail. They knew not of FTP.

Re: Create - A new kind of web editing interface

#29

Post by nvictor »

many people already suggested that the idea is not novel. this implementation doesn't add what i wish we had in a modern inline content editing framework: structure.

wikis had it for a while now. [[newpage]] anyone? i am wondering how difficult it would be to take wikis out of their textareas.

the other concern is naturally security.

Re: Create - A new kind of web editing interface

#30

Post by timclark »

Newgy wrote: post #22
veb wrote: post #8

Earlier quoted context omitted.

Does it need structural options? 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 wh…

Same problem here. The admin site structure of the typical CMS is an abstraction that makes obvious sense to us developers, but not necessarily to the content managers. Inline is the future.

Most of the expensive CMS products have edit in place, so a user can just click and edit. This does come with quite a large overhead in pageweight in my experience.
Post reply on HN