Tag: Experience Editor
When building Sitecore-powered websites, it’s easy to forget about the content authoring experience. We live in this system and we’re used to its quirks, so we’re not often reminded that others–like our content teams–don’t share the same level of familiarity and comfort. We also can forget that making Sitecore friendlier for our content team is critical to […]continue
When building a new site using BrainJocks SCORE, are you paying attention to the styling of the Experience Editor view?
Some project team members may consider this a waste of time, especially for projects that are low on budget and/or need to be finished very quickly. But neglecting Experience Editor has meaningful consequences – and your Content Administrators will be the ones who suffer. A frustrating authoring and editing experience can make it impossible to leverage the full power of even the best website.
Our ultimate goal with BrainJocks’ projects is to style Experience Editor to look as close to the front end of the site as possible, optimizing the admin experience. I’ll explain two types of Experience Editor styling that we address when we build websites.continue
If you are passionate about testing automation in Sitecore, sooner or later you will want to mock Context.PageMode.IsExperienceEditorEditing (or Context.PageMode.IsPageEditorEditing in pre-Sitecore 8) properties. This post will give you step-by-step instructions on how to do that using Sitecore.FakeDb.continue
Sitecore.ExperienceEditor.js Sitecore 8.0 introduced SPEAK-ified version of the Experience Editor ribbon. If you built or ported your own Page Editor extensions you have probably followed in Sitecore footsteps and used SPEAK pipelines along with Sitecore.ExperienceEditor.js APIs (I know I did). Your code might look like this: you might also be leaning on a few other […]continue