Show HN: Instant CMS as a Service on any element (with contenteditable)
copybar.io
copybar.io
I integrated Redactor as another editor option in Create.js a while back, but it looks a bit strange because it changes the styling of the currently active content area. Other than that it is very simple and clean!
Another valid editor option is Aloha, http://aloha-editor.org
You can use any (or even all) of these with Create, or integrate your own. The next editor I'm looking to add is CKEditor 4, as it also has an inline editing mode: http://nightly-v4.ckeditor.com/3627/samples/inlineall.html
Took a long look at Aloha, but it has such a big footprint that it scared me away.
Thanks for the pointer to CKEditor 4, I wasn't aware they had an inline mode.
Would be great to see some keyboard support in the future however. eg Super-B/ctrl-b for bold. Haven't tested on Windows, but OS X is lacking working functionality in the latest build
Let me explain ...
Like AOL, Facebook is a walled garden reproducing what is standard and open on the web/internet as a whole. AOL had AOL email, Facebook has html homepages, and RSS/ATOM
But "people" cannot create their own content - they cannot write HTML, host web pages etc. But contenteditable fixes all that - and with the clever Dropbox tie in, anyone can start with a templated page, drag and drop images from their own desktop, (#) and publish themselves.
Add in RSS via Javascript and its all over.
(#) oh yes drag and drop images onto a web page - its soooo cool. Aloha supports it at least.
Also, there are a lot easier ways out there to publish your own content online (Weebly, Tumblr, etc) but that doesn't seem to have stopped Facebook.
Whilst it is of course possible to replace a CMS with flat HTML files what is the main target Market you see for this?
Or is there anyone out there that knows of a library that could possibly do this?
Is copybar dynamically replacing the content and then next time when the page is loaded javascript replaces the content by fetching the value from copybar CDN?
At least it looks like copybar is not changing the actual CMS database content values. Please correct me if I misunderstood the mechanics.
The problem with dynamic replacing would be: 1) search engines get the old text 2) original CMS editing functionality becomes useless for that specific node.
Thanks! Yeah, we're using the CDN to dynamically display your edited content.
When editing an element, we invalidate the cache on the CDN. It may take a minute or 2 to propagate.
Search engines these days execute Javascript so it can index this dynamic text. However we also have a backend integration solution (via a simple rest call) for people who would rather serve the content from their web servers directly.
I can't actually think of a practical use case for the Pro-xx accounts. A fairly simple blog would easily have a 100 assets or more. Even a simple corporate blog would have 100 assets after a few months.
In particular, I'm trying to figure out what your expected use case is for the Pro-20 account ... what kind of site would I have only 20 assets that I want multiple editors to be able to change?
Websites tend to be many asset/many editors or many assets/few editors. I can't think of too many few assets/many editor situations.
- You id="mask" element has a higher z-order than your formatting popup making it impossible to select styles in the demo.
- The blink from the original to the edited content is kind of jarring. Not sure where your servers are, but here from AUS the lag was very noticable.
- This is a peeve I have with all editors: When you select a H1,2,3 etc style the entire block is styled. This is the opposite of what users expect. Instead you should break that fragment out and run your execCommand on it. This way only the selected text receives the style and your users aren't left scratching their heads :)
- Consider adding an in-line editor for in-line images. Popping over a modal editor onmouseup is not intuitive for your average Joe.
(Sometimes I wish people would go back to the golden days of "software as a product" instead of the current "everything as a service" way of selling things... I just wanna pay for it once, include it as a plugin for my CMS and MAYBE pay extra for some kind of support... and yes, I would be willing to pay for an upgrate to the next version too...)
Also, something interesting: you can use the same element across many different pages. It will repeat the same content, but still count as only 1 element.