Editors can now specify the language in which the text on a web page is written.
Scrivito JS SDK 1.22.0 Released – Featuring Language-Aware Search
Posted on
Introducing language-aware search for better search results
Whether a visitor uses your site search, or an editor uses the search sidebar, Scrivito now takes the language of the documents into account. As a result, language-specific common words (stop words) are ignored, preventing unrelated hits from showing up. Also, stemming is now applied based on the language of the pages, meaning that, for example, singular and plural forms are treated equally, increasing the quality of the search results.
The JavaScript API now also includes an according language() method as well as the _language attribute.
A sidebar for your websites!
Are you managing multiple websites with Scrivito?
Your sites are now accessible via a dedicated sidebar and no longer via the hierarchy. This helps you keep track of your sites and always have the most recently used ones at your fingertips.
Adding subpages directly
Adding a subpage using the main menu or the submenu in the hierarchy sidebar usually first opens the dialog for selecting the page type. Now, if, due to page type restrictions, only a singe type is available, the dialog is not opened anymore but, for your convenience, the menu item lets you add such a page directly.
More meaningful page titles for editors
In previous versions, the editing configuration of an object or a widget class allowed you to customize the title their instances should have in the Content Browser and in properties views. For this, the titleForContent callback can be provided.
Sometimes, for example with homepages, a label meaningful to editors cannot be derived from the visible content alone. For handling such cases, Scrivito introduces a new attribute convention: contentTitle.
As a default, i.e. if no callback has been provided, titleForContent now first looks for a contentTitle, and then, if it’s empty, for a title string attribute. This makes it possible to provide a custom title for editors (contentTitle) as well as the regular title to be displayed to visitors (title).
API for retrieving the current working copy’s ID and title
To better support customizing Scrivito’s editing interface, the SDK now includes an API for retrieving the ID and the title of the current working copy, Scrivito.currentWorkspace().
Further improvements
History 5.0.0 support
You can now use the history library in version 4.10.1 or 5.0.0 with Scrivito.
More great blog posts from Andreas Viebke
Scrivito JS SDK 1.35.1 RC 1 Bugfix Release
Bugfixes All API keys now work properly in Node.js environments In the Scrivito JS SDK, version 1.35.0, we added support for private API keys in a Node.js environment. Due to an encoding error when passing the credentials to the Scrivito backend, some keys didn’t grant access to restricted...
Scrivito JS SDK 1.36.0 RC 3 Released
Introducing data details pages
In an earlier Scrivito JS SDK release, we introduced data lists for seamlessly integrating not only individual data items but also collections of such items into your Scrivito app. Now, we are happy to present an even more powerful feature for data integration: Data details pages that can display...
Your Profile Image on the Sidebar
Latest updates to edit.scrivito.com
Logged-in editors can now see their profile image If you have added a profile picture to the IdP (identity provider) account you use to log in, it is now displayed on the sidebar instead of your initials. For example, if you log in with your enterprise account, Scrivito uses the image from your...
Scrivito JS SDK 1.35.0 Released
This release introduces multi-line editing for string attributes, and improves several development-related aspects, also in the context of Node.js. Improvements Multi-line editing for string attributes As a developer, you can now enable multi-line editing for string attributes in the “Properties”...
Scrivito JS SDK 1.34.0 Released
Featuring data lists with placeholders
Placeholders in lists In the previous Scrivito JS SDK release, we had introduced placeholders as a means to incorporate personalized data into textual content. Building upon that, we are excited to announce that in this release, we have expanded the functionality of placeholders so that they can...
Scrivito JS SDK 1.33.0 Released
Featuring placeholders for data items
Weaving data into website content using placeholders Editors can now insert placeholders representing specific pieces of data into textual website content, e.g., for personalization purposes. When the website is then visited, these placeholders are dynamically replaced with data provided by the...
Working More Easily with Widget Properties
Latest updates to edit.scrivito.com
Editing widget properties on the sidebar For more convenience and uniqueness, the properties of any widget can now also be edited on the sidebar after clicking the “Widget properties” menu item of the widget concerned. The editing interface uses the sidebar that originally was dedicated to the...
Comparing Any Published Content Versions from the Publishing History
Latest updates to edit.scrivito.com
Selecting the published content versions to compare The publishing history now lets you compare pages in any version of the published content with the corresponding page in any other version. Several of our customers had asked for this to be made possible. In more detail, determining the changes...
Working more Easily with Websites
Latest updates to edit.scrivito.com
Improved “Sites” sidebar The “Sites” sidebar panel is now clearer, so you can more easily access the language versions of the currently selected website. The order of the language groups in the “All Sites” section is now fixed, which makes it easier to navigate the list and pick a site. The...
Switching to Neoletter Made Easy
Latest updates to edit.scrivito.com
Switching to Neoletter made easy The Scrivito editing interface now features a sidebar button for conveniently opening the Neoletter UI associated with the Scrivito CMS concerned. Thank you for using Scrivito! Please let us know what you would like to see improved.