```html

Content

This section aims to explain the concepts involved in the development of Content services, assisting the developer in creating customized services using the facilities of the Content Framework. For more technical information about Content, refer to its API.

The Content is a framework that extends the DOUI by adding content management functionality.

Services can also be created through the Content Management Service Creation Assistant ( Wizard ).

The definition of a content service is equivalent to the definition of a DOUI service, but there are configurations in servicedefinition.xml and douidefinition.xml that can be used only for services that utilize the content framework.

A service can be defined as a content service by placing the attribute type with value lum_content in the service node. The implementation of a content service is done by the class ContentService. Therefore, if you wish to implement a class for a content service, it is necessary that it extends the class ContentService. The ContentService extends the DouiService by adding specific functionalities of content.

Content Service Interface

An interface can be defined as a content interface by placing the attribute type with value lum_content in the interface node. The implementation of a content interface is done by the class ContentServiceInterface. Therefore, if you wish to implement a class for the interface, it is necessary that it extends the class ContentServiceInterface. The ContentServiceInterface extends the DouiServiceInterface by adding specific functionalities of content.

For each content interface, there can be a block defining that interface in the douidefinition.xml file. If the block is not present, a default structure is used.

The ContentServiceInterface makes the necessary calls to the content framework, so that the interface can be defined using the facilities that the framework offers.

Types of Content Interfaces

In a manner equivalent to DOUI, in addition to the type lum_content, there are other types of content interfaces that have greater specialization or special characteristic. All of them extend the class ContentServiceInterface. The default structure of the interface (the one used if the interface is not defined in the douidefinition.xml) also varies according to the type. There is a type of content interface equivalent to each type of doui, as shown in the table below:

DouiInterface	ContentInterface	Information
`lum_douiList`	`lum_contentList`	Interface that renders a complete list of content from the service instance.
`lum_douiQuickList`	`lum_contentQuickList`	Interface that renders a list with the first contents of the service instance. The default quantity is five contents.
`lum_douiDetails`	`lum_contentDetails`	Interface that renders the details of the content when selected from the complete or quick list. When the details page is accessed directly, by default, the first registered content is displayed. However, when content is accessed from the list but has been removed in another session, the details interface does not display content.
`lum_douiAdministrationList`	`lum_contentAdministrationList`	Interface that renders an administrative list of registered contents.
`lum_douiAdministrationPropertyPage`	`lum_contentAdministrationPropertyPage`	Administrative interface for the list of contents.
`lum_douiAdministrationAddPropertyPage`	`lum_contentAdministrationAddPropertyPage`	Pop for adding contents.
`lum_douiAdministrationEditPropertyPage`	`lum_contentAdministrationEditPropertyPage`	Pop for editing contents.
`lum_douiAdministrationEmbeddedAddPropertyPage`	`lum_contentAdministrationEmbeddedAddPropertyPage`	Addition screen whose rendering is on the page and not in a pop.

```