I agree with Jun. We need several services that can be used to build a nice CMS user interface.
ETP will use just a few of these services, leaving out workflow, and using a very simple user interface. Other applications might need to use different features, or present them to the user in a different manner. One CMS UI for everyone is the wrong way to go.
So here are some services we will need to build:
Categorization: already in the content-repository. Needs work, we might want to make this a more general service to allow categorization of any acs_object.
Related Items: this is implemented in the CR, and also generally as acs_rels. We need to make sure there is an easy way for developers to tap into this feature.
Multimedia upload and management: Image management, and relating the images to content items to appear in templates. I am not sure if this is covered anywhere.
Templating per content item: this depends on the CMS implementation. The current CMS has this.
What else?
