Humbled and pleased to announce that I’ve been again named a “Most Valuable Professional (MVP)” by Sitecore® for a second year running (2018, 2019), winning in the area of the Strategy. A lot of hard work and focus on solving clients’ problems via the Sitecore platform has paid off once again. Looking forward to another active year in the community!
Some info about the program below:
Now in its 13th year, Sitecore’s MVP program recognizes exceptional professionals from the Sitecore community who actively share their expertise of Sitecore products to advance the future of customer experience and drive organizational change. A distinguished group of 315 Sitecore experts from the more than 12,000 certified developers and more than 20,000 active community participants, Sitecore MVPs’ are awarded for the quality, quantity, and level of impact of the contributions they make by sharing their product expertise and mastery of the Sitecore platform with other Sitecore partners and customers.
“The Sitecore community is renown as a place where members can easily collaborate and benefit from the vision and technical knowledge of one another,”
Pieter Brinkman, Senior Director of Technical Marketing at Sitecore.
“Within this community, MVPs set the standard of excellence for product expertise, enthusiasm, and willingness to donate time and energy to help customers and partners realize the full power of the Sitecore platform. Their passion is instrumental to the ongoing success of the Sitecore ecosystem.”
The Sitecore Experience Platform™ combines web content management, omnichannel digital delivery, insights into customer activity and engagement, and strategic digital marketing tools into a single, unified platform. Sitecore Experience Commerce™ natively integrates content and commerce so brands can fully personalize and individualize the end-to-end shopping experience before, during, and after the transaction. Both platforms capture in real time every minute interaction—and intention—that customers and prospects have with a brand across digital and offline channels. The result is that Sitecore customers are able to use the platform to engage with prospects and customers in a highly personalized manner, earning long-term customer loyalty.
More information can be found about the MVP Program on the Sitecore MVP site: http://mvp.sitecore.com
This year, along with Dominic Hurst of Valtech, I was very fortunate to have presented at the Sitecore Symposium in Las Vegas, Nevada. Both Dominic and I have worked on a variety of Sitecore installations and over the years have noted some mutual industry observations:
- The role of the Content Author in modern CMS solutions has evolved into a multi-dimensional job. Too often these every-day heroes have to fight inflexible and uninspiring solutions to overcome the even smallest tasks
- Many organizations spend the lion’s share of their budgets on CMS implementation, yet pay little attention to the efficiency of the operational processes that enable it
- Poor authoring experiences can lead to UX erosion over time. Bad AX → Bad UX → Bad CX
- Content authors are rarely empowered to aid in design, personalization, and performance analysis
Together at the Symposium we decided to address these observations and present our top 10 tips for organizations to empower their content authors to deliver real value on a daily basis. Many they can enact right away. Below are links to 10 blogs posts that cover each of these points in greater detail. We hope you enjoy these posts and, of course, please reach out to either of us to continue the conversation. Dan – @sitecorelations; Dominic – @dh_analytics)
- Provide access to non-explicit fields in Experience Editor
- Simplify rich text embeds
- Make it easy to do the “right” thing
- Optimize data template architecture for greater usability
- Dynamically nest local components with pages
- Use branch templates to create structured content models
- Get your content authors involved in the design process
- Be a custodian for chang(ing content)
- Embrace governance, add guard rails not gates
- Combine the authoring experience with analytics
Special thanks to Nicolai Winch Kristensen of Sitecore for coordinating and moderating our Sitecore Symposium presentation. May the force be with you!
Three of the guiding principles I always keep in mind when trying to build usable systems in Sitecore are:
- Reduce the number of decisions a content author has to make
- Reduce the number of things that require editing in the first place
- Make it easy to do the “right” thing
One of the greatest tools for ensuring that these three things are achieved are Sitecore branch templates. Branch templates allow creation of item hierarchies in a singled click using dynamic placeholders. You can instantly create complex but predictable multi-tiered structures so that an author need not recreate these manually.
A content author creating yet another news article need not see a blank slate each time when it’s likely that this content type is highly structured and will have instances of the same components in the same layout, at least as a starting point. Below are some examples of branch templates for pages that specifies a core collection of default components to be included with each new instance of the page.
This is even more useful for creating multi-tiered structures such as office microsites or any other repeated content grouping that all have the same basic hierarchy. Why have content authors doing data entry for content objects that are predictable and repeatable? This is time-consuming, prone to error, and discourages consistency. Companies tend to treat content authors time as expendable, but it’s really not when you consider the cumulative total of all of these tasks and micro-interactions with the CMS.
Leveraging branch templates requires a holistic approach to content modeling that is best done when a platform is being constructed as it requires some forethought and consensus on standardization. That said, it’s not impossible to inspect existing structures and create supporting branch templates for use moving forward. Finding ways to accelerate repetitive tasks may just improve content author morale as much as their efficiency and free them up to do higher value work!
Information architecture and system design decisions can have a major impact on the ease with which content can be created and managed in Sitecore. Authoring experience is not always front-of-mind as architects and developers are shaping a system, but this can prove short-sighted as content teams begin to build content in the system.
During recent authoring experience audits of clients’ Sitecore platforms, I have noticed one key thing negatively impacting author efficiency. Many times, local components are not grouped with their parent page. While this is common and expected for globally shared components, it’s not recommended for unique instances of components referenced only by a single page. In one such case, there was a total separation of pages and components. There was an entirely separate directory for components that mirrored the page hierarchy manually. The rationale was that it kept page objects in the tree simple and uncluttered (which was true) but the end result was that authors were pre-creating all necessary components for a page ahead of time rather that authoring a page inline in Experience Editor. Rather than simply choosing from a list of allowable components and dropping an instance on a page, the first thing the content authors were required to do was establish a link to an existing data source. This really threw a wrench in the inline editing experience and was affecting content authors impressions of Sitecore – thinking “that’s just how it works.”
To allow for greater automation and improve author efficiency, dynamically nest components locally under each page object so that pages can be more quickly constructed and fully edited inline.
Through use of branch templates and standard values, a local Components folder can house all unique instances of components applied to a page. The content author doesn’t have to spend a lot of time thinking about where they should go. It reduces the number of decisions they have to make and speeds the authoring process. If you want to get fancy, you can even include sub-folders to keep multiple instances of different kinds of components organized (e.g. multiple rich text blocks, images, or videos).
This approach also simplifies the publishing process when you want to publish all components along with a page. Since these are sub-items, this relationship is easier to deal with rather than referencing components as related items.
This is something I have had a lot of success with and as the trend towards greater componentization in WCM systems continues it’s becoming a standard approach in the platforms Velir builds.