Enterprise grade editorial experience with Drupal

The way we build CMS systems has changed: Today we build frontends independently from backends.

Because the frontend can easily be changed, the editorial experience in the backend has become an important differentiation criterion for choosing the right CMS system.

At the same time editors like to edit content directly in the frontend (WYSIWYG), instead of only working in a structured backend.

At 1xINTERNET we have developed new modules to improve the editorial experience of editors, in order to meet the expectations of our clients: One module allows re-using entities as content templates with a similar UI as Google Docs. Another one, that we are currently developing, allows to edit entities directly in the frontend.

Both modules are built on top of Drupal, using as much of the API as possible. At the same time the integrations are lightweight and can easily be extended. The plan is to contribute both modules.

In this session I will demonstrate
- what we consider being an enterprise grade editorial experience
- how the template module works and how it integrates with editorial workflows
- how editing content directly in the frontend works, and how Drupal’s API is used for this