Creating awesome content editor experiences
There are a lot of ways to build structured content in Drupal - fields, blocks, nodes and paragraphs. These do produce a lot of database tables though and the administration user interface built with Drupal can get a bit clunky the more content is produced.
This talk looks at these issues and asks the question, when reusability isn’t a requirement, is it okay for structured content to be built in the body field? Does every call to action, every image, every column based layout really need it's own entity and database table?
Modern WYSIWYG editors such as CKEditor provide a powerful plugin system and clean, extensible user interface for building structured content elements. Drupal integration through modules such as entity_embed allows us to retain structured data in the backend when reusability is required.
We’ll explore when it's right to use fields, when it's right to use entities within other entities and when it's fine to manage your content through the WYSIWYG.
The talk will use real examples from actual Drupal 8 client sites.