Bronsdijk,

You are completely correct about this. That is also the problem we are facing when we talk to some content editor.

They like to see a sitemap navigation, they like to see pages directly and able to add pages into the sitemap node directly. In one extreme case, we had to build another interface for editor, and name the content item as the name of "page", so editor think that are editing pages, but in fact, they are editing content item. Those editors also just like to use a Html editor for complete page content and also like the inline editing feature.

It is pretty possible to do it this way because of the Kooboo API and inline editing features, but it is not the recommended way. People thinking in this way because they still think that a website should be built mostly by static page, while we think the future should be mostly dynamic content.

Kooboo has an user rights management, you can easily configure users to have access to only certain menu. For example, you can configure an user to have access to only one folder called "news", so when he login, he only see a list of news and able to edit or click "new" to add a new news. The news input form is pretty clear and can not be more user friendly any more.

If we are able to train content editor to get used to concept of dynamic page content and the interface of Kooboo, that will be the best, otherwise we have to implement something special for them.

Regards,

Vincent

I was thinking the same think but with the content area(but you probably meant that?).
I think it would begood to be able to oversimplify it for content editors.

Sounds like a supreb idea, i was thinking in the same direction.
I guess that includes adding objects inline as well but if not it should be considered.

One note though regarding localization. I think your localization concept is very good when it comes to managing larger multilanguage sites with different flavors and personality. But it becomes a bit bulky(atleast with the little ive seen of it sofar) when it comes to small company sites(1-2-3 person companies and such). In my experience they mostly wants all content to be identical(exept perhaps that news x should only be visible on main language wich publish solves) but in the different selected languages.
That means that, if i understand correctly otherwise please correct me, today one have to go to the main content folder(app or root) and add for example a news object. Then they have to browse to ach language site, find and open the news and translate and publish each news.

What im proposing as a suggestion if you enhance the inline editing(if its feasible) is a function to have the add / edit screen with tabs of the localised languages. So if a person have a 2 language sites and wants to add a new news item for example he click the add button on the site and gets the form like done today. But from there he can switch tabs to the inherited objects as well and localize them on the spot.

Since im green on kooboo i dont have anything to say about the technical consequences of this but that is my suggestion to acommodate small company needs. And since your permission system the user would be limited to seeing the inherited items for the app that he / she has permissions to.