Page tree
Skip to end of metadata
Go to start of metadata

Date

Attendees



Main Discussion

Background

Landed in a project when it was a bit messy, this was at the time that there was one template and big list of components within one template.


Input 1

If you have users with more expertise, one single template with all the components. However if this expertise is not there, is more difficult for editors to know about all the components beside extended documentation.

Input 2

There is a project that we have a "universal" template. The main problem is the layout component (2-4 columns), no way to know what is in the grid. Now when we have hundreds of pages, and we want to do a re-design, it is impossible due to it is not known what is inside of the layout. 

No freedom to define layout. The approach is to separate the content from the representation. Authors/Editors should not be creative on design.

Input 3

We make that our designers understand our component base design architecture.

We use prototype yaml where the templates inherit most of the components and then some customization. So is kind of an hybrid solution

Input 4

Specific templates + a fallback page which allows more component combination. This fallback page sometimes is limited to certain roles with higher expertise.

Input 5

More flexibility requires more documentation and the expertise is difficult to go from editor to editor.

Is kind of a trap approach due to later on is more difficult to maintain, it will require more consultancy about how to use component to achieve something.

Strict template will bring more request for any new thing editors want to do, but later will facilitates re-design due to there is more isolation between content and template.

Input 6

Hybrid solution with specific template and a template with much more flexibility. That template usage is limited to Product owner/superuser.

Input 7

Recommendation to use areas with some variants but limited

Whenever a lot of template use page availability to limit the amount of options to choose and make it easier for the editor

Related topics

  • Page availability
  • Sanity checks for empty components

Summary

Highly depends on:

  • Customer, requirements and/or use case
  • How many editors we have, the bigger the more guidelines and strict needs to be to keep control


In general hide layout from non-superusers to disconnect content from template as much as possible.