Video of how a text field without translations behaves

Video of how a text area with translations behaves

Video of how a text field without translations behaves

Text fields in Picturepark have an additional option to render Markdown. Using Markdown in text fields allows for basic formatting like the use of headlines, bold, italic for descriptions, press kit content, or product details, to highlight specific areas or structure longer texts.

Picturepark shows an editor with a side-by-side view for formatted and unformatted text.

Picturepark uses the following component for rendering: https://markdown-it.github.io which offers an online demo. Please ensure that all plugins (checkboxes at the top) are disabled in this demo, as Picturepark does not support any plugins for now. Some basic examples of Markdown syntax are:

Text fields allow limited control for user input. Whenever you work with text fields you may have typos or dummy text. The only control present for text fields is the definition of a regular expression for text input. 

Text input is always unstructured content. 

You can add a filter for text to the content browser. Be aware that you might end up with a lot of filter values as text entries can differ a lot, also they may describe the same topic. Consider using Tagbox fields to avoid three different filters for the same topic:

• Title: New Office Location in Aarau
• Title: Aarau New Offices
• Title: The new location of the Aarau Office

Text input is analyzed in Picturepark. Analyzers are explained in the Search Analyzer Section. Analyzed means Picturepark extracts individual relevant terms, whereas relevant depends on the Analyzer. 

• Text without translations is analyzed with a simple analyzer. 
• Text with translations is analyzed with the language analyzer. 
• Further analyzers can be configured. 

You can use translated text as a sort field for a Channel. You can configure the field itself or the specific language of the field.

For the field itself, changing the UI language will trigger the sorting to work against the corresponding translation value.

For the specific language, the sorting will also happen only on the configured language. This enables you to sort on metadata languages other than English and German if the values are translated. 

Use the Text field for:

• Product Codes
• Titles
• Descriptions
• URL

Search: Find Items by Product Codes (Solutions)

Search: Find Product Information in Translated Description (Solutions)

Search: Find Items with specific values in text fields (Solutions)

Search: Find Items with values in translated fields. (Solutions)

Search: Find Items with Exact Term in Translated Field (Solutions)

Display Pattern: Show Text as Headings (Solutions)

Display Pattern: Text (Solutions)

The Liquid filter | translate returns the value that matches the default language. 

To get specific language values you must provide the correct language abbreviation: .de / .en

Add the name in singular or plural depending on the use case. 

Avoid adding the required language in the label (Title English, Titel Deutsch) as Picturepark shows the language in front of the field. 

The ID fieldis the ID of your field, which is used to link to this field. The field ID is always lowercase. The field's ID is set when creating a new field using camel casing. You need the field ID for the configuration of filters or display patterns. 

The ID is automatically created from the name you insert: 

• Example: You insert the field name "My NeW fielDs #1 Purpose?
• Automatic Id: myNeWFielDs1Purpose

The option to render the text values as Markdown, including side-by-side Markdown editor. Picturepark offers:

• Default rendering: The text input is just text without any formatting.
• Markdown rendering: The text input is in Markdown syntax and bold, italic and links are rendered correctly.

Markdown will only be rendered in the Content Item Detail View, not in Display Pattern or list views.

Only for input validation means you can force the user to insert a valid email address, but you cannot append something after input - this can be achieved with a calculated value. 
A JSON Schema regex can be used. See here for valid examples: https://spacetelescope.github.io/understanding-json-schema/reference/regular_expressions.html
North American telephone number with optional area code - 555-1212 is valid but (800) Flowers is invalid:

(\\([0-9]{3}))?[0-9]{3}-[0-9]{4}$

You will not be able to enter text in this field if switched on. The value pattern will be displayed in view mode. 
Due to the performance for creating content or list items that have relationship fields, a limitation on the calculated values is present. A calculated value won't be able to access the data of the linked (and resolved) list items. It will only be able to access base content information and the other metadata information (other fields, fieldsets, and relationship values). If the values of linked list items are used, their value is simply not resolved, but the rest of the specified template is rendered. No error message appears if a calculated value cannot be resolved that part of the calculated value just doesn't display.

Once the calculated value setting is switched on you cannot just switch it off to remove the calculated values.

• You can update the calculated values.
• You can remove the calculated values by batch editing all affected items (List, Content) and remove the value or you can remove the field.

Monaco Editor which allows defining the calculated value pattern in Liquid Syntax.

Display Pattern: SEO Friendly Title (Solutions) — A slug is an SEO friendly title you use for images, videos, or complete press kits when sharing them on social media. Picturepark can create the slug for you using any value from any field, replacing spaces with dashes, and even pretending the correct domain.

Display Pattern: File Metadata in Layer Fields (Solutions) — You may want to show the file extension or original filename (standard file metadata) in calculated text fields in a layer. You can make those available to the search and have some basic information shown.

The Boost factor field setting will boost the values in the search and help you define the relevance of the content for your users. The boost parameter increases the relative weight of a term (with higher boost values) or decreases the relative weight (with lower boost values), but the increase or decrease is not linear. In other words, a boost of 2 does not result in double the score. You can select between 1, 10, 25, 50, 100, or 500. 

• Boosting in a list is for the search in fields while tagging.
• Boosting in layers is for the content browser search.

Picturepark checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search boosting them, you may revisit this idea based on your subscription plan limit.