Until the release of Enonic XP 7 the Content Studio app used to be a part of the XP distribution package. Content Studio 2.0 is the first version released on Enonic Market separately from XP. It is compatible with XP 7.0 and will not work with earlier versions. This release includes some important features, as well as a number of major improvements and bugfixes.
In previous versions Context panel (previously "Detail panel") was available only in the Browse Content view. Starting from version 2.0, the panel is available in the Content Edit view as well. User can now access widgets without having to switch to or open the Browse view. The panel can be opened and closed by clicking the cog icon in the top right corner of the view.
Compared to the Context panel available in the Browse Content view, in this view the panel adds the widget for managing selected content, such as adding new components to the page or configuring existing page components.
You can find more information about the Context Panel and widgets in the dedicated section.
Schedule, Settings and Access steps of the Content Wizard form are now represented with icons in the navigator toolbar, to separate them from the custom steps of the form. Clicking the icon would scroll the form down to selected step.
Unlocked lock icon for the Access step means that this content is accessible by everyone (user Everyone has at least "Can Read" permissions). Locked lock icon means that read access is limited.
Content Studio 2.0 enables automatic preview of the media content (video, audio, PDF, DOCX etc.) directly in the preview panel.
Table features in the Rich text editor have been greatly improved and now enable changing column width, cell spacing/padding and border width via "Table Properties" modal dialog (right-click the table and select "Table properties" from the context menu).
The same context menu can be used to add and delete rows and columns, merge several cells into one etc.
Image dialog of the Rich text editor now allows user to adjust relative width of the image. Check off "Custom width" checkbox in the modal dialog and adjust the width using the drag control.
Content Studio 2.0 introduces a new feature in the rich text editor called "Image styles". Image styles consist of both client side styling (css), and image service rendering specifications.
The rich text editor was previously limited to pre-defined and hard-coded styles, such as
cinema (21:9) or
square(1:1). Now, application developers may define custom styles that control both server side rendering aspect ratio, and specify classes to annotate the specific image.
Read more about defining custom image styles in the dedicated section.
XP 7.0 introduced a new value for portal rendering mode (
mode field in the HTTP request object). In addition to edit (when content is being edited in the Page Editor), preview (preview of a draft version) and live (preview of a master version), when content is rendered in the preview panel of the Content Studio the
request.mode will have a value of inline.
Previously, Tag input always allowed tags from all available content in the repo. Now tags are by default limited to current site. You can use
allowPath config to adjust this limit and allow content outside of the current site.
Allow tags from other sites
<input name="MyTag" type="Tag"> <label>Tags for this content</label> <occurrences minimum="0" maximum="0"/> <config> <allowPath>*</allowPath> </config> </input>
XML schemas of content types, pages and page component descriptors now support optional
description field which, if filled, will be shown in the Content Studio UI.
If set, content type description will be shown under display name inside the "New Content" modal dialog.
Description in content type schema
<content-type> <display-name>Author</display-name> <description>Create authors to be selected on blog posts</description> <form/> </content-type>
If set in the page descriptor schema, page description will be shown under page root in the Page Components tree and also the page descriptor dropdown inside the Inspect component widget.
Description in page descriptor schema
<page> <display-name>Page</display-name> <description>Front page of the Superhero site</description> <form/> <regions> <region name="main"/> </regions> </page>
If set in the component schema, description will be shown under component’s display name in the Page Components tree and components descriptor dropdowns. Description is supported for layouts and parts.
Description in component descriptor schema
<part> <display-name>Featured</display-name> <description>Feature a post in large format</description> <form/> </part>