3 ways to improve your content author experience with Keystone

1. Better social sharing through OpenGraph

The Open Graph protocol is used by major social sites like Facebook to understand your webpage and accurately represent your content in a social graph or timeline. By applying the right meta tags to the pages of your website, Facebook and other social sites can create rich content displays.

If you want to code the HTML yourself, you can do so following the documented meta tags at http://ogp.me/. A quick example:

<html prefix="og: http://ogp.me/ns#"> <head> <title>The Rock (1996)</title> <meta property="og:title" content="The Rock" /> <meta property="og:type" content="video.movie" /> <meta property="og:url" content="http://www.imdb.com/title/tt0117500/" /> <meta property="og:image" content="http://ia.media-imdb.com/images/rock.jpg" /> ... </head> ... </html>

To provide content authors with this capability in Sitecore, Keystone implements the Open Graph meta data. Tagging your page is as simple as filling in a few fields:

The OpenGraph capabilities in Keystone will put a smile on your marketing team and content authors’ faces, all with minimal development activity.

2. Building responsive designs in Sitecore

Given the mobile-first revolution, many website stakeholders will put careful consideration into the requirement to support smart phones and tablets- often through responsive design. The problem with this approach is that despite your best efforts, it can be difficult to foresee all of the potential responsive scenarios, particularly in the case of a new landing page, campaign page or microsite.

Keystone solves this problem by giving access-granted content authors the freedom to control content components in order to manipulate the way content will behave on a website page.

It does so in two ways:

  1. Keystone provides a library of responsive grids. Built into each grid component is a set of rules that will make the content flow properly on different screen sizes.
  2. Content authors are given the ability to modify - on a component by component basis – the visibility of the content on different sized devices.

By combining these two capabilities content authors can build pages that cater to their specific mobile requirements, likely based on audience research conducted with data and analytics.

3. Workflow and content author enhancements

Keystone includes several Sitecore UI and workflow enhancements that extend the native capabilities of the Sitecore system.


Keystone includes the following custom gutters for the Content Editor:

  • Comments: displays an icon if the item includes content in the Comments field
  • Personalization Presentation: displays an icon if the item includes personalized content
  • Published: Keystone has two display states: one icon indicates the content has never been published, while the second is shown when content between the master and web databases differs
  • Tests Enabled: displays an icon when the page has tests enabled

Workflow - component publication

Keystone ships with a single reference workflow, simple workflow that can serve as the basis for your own workflow(s). This workflow is intended to be applied to data templates that represent a webpage. The key benefit of this workflow is that it works in concert with the component workflow to ensure all items that constitute a page are moved through workflow and published together.

The component workflow is provided as a means to link the datasources of content components to pages, and ensure that updates to pages and their datasources can be treated as a unified package for approval and publication.

When you assign the component workflow (/sitecore/system/Workflows/Component Workflow) to the datasources of your components, Keystone bundles components with their pages. A custom workflow command can then be used in the page workflow to approve the components and send them for publication. The publish components action can be added to any page workflow by referencing the Keystone code: Keystone.SBL.Workflow.PublishComponents, Keystone.SBL.

Email actions

Keystone includes two custom email actions that can be used to send an email to a group or the person who started the workflow. You can add these actions to a workflow using the insert rules by referencing the respective Keystone classes.

Tokens supported in the body of the message are:

  • {title} – DisplayName of the Item
  • {livelink} – the published URL of the item
  • {editlink} – the link to the content editor for this item
  • {updatedon} – last updated date of the item
  • {updatedby} – last updated by user
  • {version} – the version number
  • {createdby} – the creator of the one
  • {createdon} – when the item was created