I think you're making some great points. I'm a developer myself. And I like to tinker. But I like to tinker with the parts of the tools that matter to the user (my personal preference). For instance, I love GitHub. It is an incredibly useful tool. But I can't change GitHub.com or edit the way it works. With Barley I think the parts that can not be changed by developers (right now, the API is about it) is the part that developers wouldn't care to change. It is a vanilla CRUD system. That's it. But the editor, templates, and the way users interact with site content is all customizable by people. A great example is our Cypress theme. http://github.com/plainmade/cypress -- It allows people to manipulate data and forms and images in ways I've never seen another CMS do. And that is at the template level.
Thanks so much for your feedback Allan.
No need for attitude, you asked for feedback. That being said:
- You call Barley an editor when in reality its just service, and expensive one at that. - Barley is marketed for developers, but in essence is a closed system that doesn't allow for modification or developers to add new functionality.
Honestly the product looks pretty good the design and available themes are decent and I understand why the concept behind barley can be useful for some people but I think you are targeting the wrong audience; developers like to tinker; barley doesn't seem to be designed to easily do that.
My advice, remarket it as a blogging platform for designers.