Defaults, cloning, referencing and content prototypes - editors' UX for similar content creation
Many websites require a lot of similar or nearly identical content. Traditional approaches to user needs have been field default values - that has limited possibilities - and cloning existing content to be modified. But everybody has seen the somewhat embarrassing copy-paste content where names or dates were forgot to be updated.
Referencing content is simple enough method, but the scope of content updates may be hard to check as content is rendered from several entities. The concept of content prototypes provides a powerful middle road approach to mass producing content allowing easily maintainable default content within a content creation process that mitigates user error compared to full cloning.
Different approaches have different uses and one is more complex to implement than the other. This session compares the strengths and weaknesses of different content mass creation strategies.
By DrupalCon Lille the content prototypes -concept will be in use on a Drupal 10 + commerce production site. Session will include comparison and concrete examples of four different content duplication strategies.
Referencing content is simple enough method, but the scope of content updates may be hard to check as content is rendered from several entities. The concept of content prototypes provides a powerful middle road approach to mass producing content allowing easily maintainable default content within a content creation process that mitigates user error compared to full cloning.
Different approaches have different uses and one is more complex to implement than the other. This session compares the strengths and weaknesses of different content mass creation strategies.
By DrupalCon Lille the content prototypes -concept will be in use on a Drupal 10 + commerce production site. Session will include comparison and concrete examples of four different content duplication strategies.