Page Comparison

How to create a Display Pattern?

The display pattern editor will help administrators create simple display patterns. The Click edit to open the display pattern editor is opened when you click on edit in any of the Detail, List, Name, or Thumbnail display patterns.

1. Open your desired schema and go to "Display pattern."

2. Find the fields on the right

3. Click on a field to add it to the Display Pattern

4. The preview is directly adapted.

5. Save your Display Pattern.

The Picturepark adds values are just added without any further formatting, so you will formatting. You get one block of text from all values of the selected fields, e.g., TitelDescriptionDateTagbox. Each field code is a Liquid Syntax Tag (if not an empty statement) containing a Liquid Syntax Object (the metadata field to use) – see Liquid Syntax for details.

You can add HTML and CSS for styling your Display Pattern. 

How to use the Display Pattern Editor?

1. The Monaco editor where you write Liquid Syntax to create your Display PatternYou write the Liquid Syntax (base for Display Pattern) in the Monaco editor.

2. The search and paging to find a specific item you want to see in the preview. To find a specific content item search for the content's id which is shown in the content detail view URL bar e.g. id:cb20faba4e3342d9a9f83191deeec115

3. The preview will give you a preview of the Display Pattern (you must have at least one content item filled out with the values in the Display Pattern for a preview to display).

4. You can add fields of the schema easily by clicking on them. Each field will be added with a liquid tag checking if the field is not empty and the liquid object which is the field.

5. Layers are only necessary for the Virtual Type Display Pattern. The fields will be the virtual type fields and additional metadata fields from layers will be available in this section.

6. Languages allow you to add a different Display Pattern per Metadata language. If you only update the default language this will be used in all other languages, the values are always translated if translations are available.

   1. Hint: Adding languages makes only sense if you use static text in the Display Pattern which then not be translated.

7. The JSON preview shows the detailed data structure of the current item you are previewing and all the available objects you have for the Display Pattern.

   1. You can use this for debugging or to check which fields are available for usage.

   2. In contentSchemaId – you find data – where you find all metadata you can use e.g. the title which is translated into en only.

      

Limitations

• For security reasons, we do not resolve Javascript.

• When you update metadata or content, the Display Patterns are updated. You don't see Display Patterns change while viewing content.

• Children do not inherit display patterns from their parents. For example, you cannot set display patterns for all file types on FileMetadata. The display patterns that you do set here will take hold for any content that is a File Type content but does not belong to AudioMetadata, DocumentMetadata, ImageMetadata, VideoMetadata e.g. for a .css file.

• Display patterns do not take permissions into account. They are pre-calculated and are not bound to user permissions. Display Patterns should therefore be optimized for your general audience and not the super admin.

• Please avoid using Picturepark icons in HTML or CSS. Currently, material design icons are treated as fontfonts, so any CSS font styling works for icons too (e.g. color or size).  Icons will be replaced in one of the next releases which will break all icon implementations. 

• No Picturepark does not support for HTML and CSS in Display Patterns e.g. in the list views the HTML will be not interpreted and displayed as text.