There is precisely nothing new about this idea, even though this code might be fresher. It would be interesting to hear how this thing addresses some of the shortcomings of the other inline editing components out there and how this is better.
It is certainly not a new idea, even we did our first implementation years ago. The main new thing here is that Create is completely backend-agnostic, only using RDFa to communicate content structure from server to editing interface, and Backbone.sync to communicate changes back to the server. But apart from that, what sort of shortcomings are you particularly concerned about?
Create - A new kind of web editing interface
61–70 of 73 posts
Re: Create - A new kind of web editing interface
#62Would be nice if more CMS backends would support this, followed by more and more editing frontends and tools. Thereby everyone could pick the component of their choice. Even different editing frontends for different unsers on the same system would be possible.
Re: Create - A new kind of web editing interface
#63There is precisely nothing new about this idea, even though this code might be fresher. It would be interesting to hear how this thing addresses some of the shortcomings of the other inline editing components out there and how this is better.
It is certainly not a new idea, even we did our first implementation years ago. The main new thing here is that Create is completely backend-agnostic, only using RDFa to communicate content structure from server to editing interface, and Backbone.sync to communicate changes back to the server. But apart from that, what sort of shortcomings are you particularly concerned about?
Submit a pull req or contact me on GitHub.
Re: Create - A new kind of web editing interface
#64Earlier quoted context omitted.
Email is actually a perfectly valid web publishing protocol. We've done quite a lot of systems where clients can publish news items by just mailing them to a certain mailbox. And http://www.deathmonkey.org/ was completely produced by sending emails from (old, pre-iPhone) smartphones on the road.
Ditto. I update my blog via email.
Re: Create - A new kind of web editing interface
#65There is precisely nothing new about this idea, even though this code might be fresher. It would be interesting to hear how this thing addresses some of the shortcomings of the other inline editing components out there and how this is better.
(it looks well done and it's interesting, but it's not a 'new kind of editing interface')
Re: Create - A new kind of web editing interface
#66Earlier quoted context omitted.
It is certainly not a new idea, even we did our first implementation years ago. The main new thing here is that Create is completely backend-agnostic, only using RDFa to communicate content structure from server to editing interface, and Backbone.sync to communicate changes back to the server. But apart from that, what sort of shortcomings are you particularly concerned about?
Would be nice to have a list of RDFa compatible backends.
Re: Create - A new kind of web editing interface
#67Earlier quoted context omitted.
I have similar issues - our website is in WordPress and despite the ease-of-use of this particular package, a lot of people just don't seem to get it. 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 c…
We're also aiming to solve this with Webpop ( http://www.webpop.com ). 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…
In this situation user would need to go to the article page to edit the actual contents.
Re: Create - A new kind of web editing interface
#68To me the novelty appears to be the backend agnostic RDFa communication with the content server rather than the inline editing. Would be nice if more CMS backends would support this, followed by more and more editing frontends and tools. Thereby everyone could pick the component of their choice. Even different editing frontends for different unsers on the same system would be possible.
But first you have to have one nice editing interface as a carrot so CMSs start supporting the needed features.
Re: Create - A new kind of web editing interface
#69Similar project: http://etchjs.com - An inline content editor *disclosure: I released this project
Maybe Etch you also run with VIE's Backbone models? http://viejs.org/
Then you could basically swap between Etch and Create with the same mark-up and server-side implementation.
Re: Create - A new kind of web editing interface
#70More generally, this would be awesome to use on a wiki.
This makes editing even more accessible.