Sitecore enthusiasts, catch your collective breath. We’ve got some exciting insights from three Arke professionals to relieve your Sitecore struggles.

Their recent blog posts may be just what you need to push past that middle of the week slump.

4 Blog Posts, 3 Authors

One of our Sitecore MVPs — Sitecore Practice Directors Martin English — detailed his experience upgrading a large multisite Sitecore installation from version 8.1 to 8.2.

Arke Sitecore Engineer Carlos Rodriguez wrote two blog posts. One discusses the use of transforms to manipulate configuration files. The other explains how to get a set of HTML to work in Sitecore’s Rich Text Editor (RTE) interface.

And Arke Sitecore consultant Neil Killen was back with more interesting thoughts about working with Coveo for Sitecore. His latest post, Troubleshooting Coveo for Sitecore, follows a January article on getting up and running quickly with Coveo for Sitecore Cloud.

Relieve Your Sitecore Struggles

Killen said he ran into an indexing issue a while back with Coveo for Sitecore. “It involved a bit of troubleshooting,” he explained.

“When you’re working with a platform like Coveo, it’s not always obvious where to start troubleshooting.”

In his blog post, Killen provides some practical steps to help you troubleshoot issues you might run into. His goal is to “get you unstuck and back doing fun stuff with Coveo and Sitecore.”

English decided to outline his upgrade experience because it took him longer than anticipated to get things up and running. “I needed to perform some updates to the client’s custom solution,” he explained.

His client wasn’t ready to go all the way to Sitecore version 9.0 yet.

Rodriguez said he wrote about using transforms to manipulate configuration files for two reasons. “I wanted to detail the steps to remind myself of what I did. I also wanted to share the steps with other developers who may be doing this for the first time.”

Rodriguez also outlined how to use RTE tools to enter HTML type. “Content authors are ofetm required to ‘copy and paste’ the HTML using mechanisms such as using the ‘Edit HTML’ option or using raw values in Sitecore’s content editor interface. I wanted to eliminate that,” he said.

To be clear, the HTML worked fine. “The difficulty lies in the process of entering that content,” he continued. “This behavior occurs because Telerik’s HTML Editor control tries to convert the content to valid XHTML.”

Want More Sitecore Insights?

If you have other Sitecore struggles, you may want to take a look at some of our other insights.

At Arke, many of our clients leverage Sitecore, a leading digital experience provider. Email Sitecore MVPs Chris Spears or Margaret Wise for more information.

About Arke

Atlanta-based Arke develops strategies and implements digital technologies for better brand experience for your customers.