Vue works quite well with Sitecore as both take a component-based approach to design – you can read more about Vue all over the web. It works great for Sitecore implementations. But we’re here to talk about how Vue works in Sitecore Experience Editor. Short answer: it doesn’t.
There are 2 main issues with using Vue components in Sitecore Experience Editor:
- If you add a Vue component into a placeholder, the Vue component does not initialize.
- If you have a placeholder in a Vue component, Sitecore will throw an error when you add a rendering to that placeholder.
Vue purists will balk about this mish-mash hybrid that we’re doing here with Vue and Sitecore. The thought behind Vue is that the markup is a visualization of the underlying data. To add to the page, you should add to the underlying data. Unfortunately, this clashes with the placeholder/rendering paradigm with Sitecore where a content author is able to add components to the page. Hence, our Vue components will be self-contained and not rendered based off of
So let’s solve these issues one at a time:
If you add a Vue component into a placeholder, the Vue component does not initialize.
The underlying cause of this is that Vue component initialization is intentional and not eager – that is, Vue is not watching the DOM for changes and initializing new Vue component as it sees them. This is due to the architecture of Vue that the DOM should reflect the data in Vue instead of Vue updating from DOM changes. We’re going to have to take this initialization into our own hands.
We can extend the default Sitecore placeholder chrome type (
Sitecore.PageModes.ChromeTypes.Placeholder) and execute our own logic after the base logic is completed by overloading the
After a rendering is inserted, we’ll need to do the following:
- Retrieve a list of globally registered Vue components.
- Look at the DOM of the inserted rendering in the placeholder that match any of the registered Vue components.
- Instantiate the Vue component.
- Reset the page chrome for edit mode.
If you look at the code below, you’ll notice a few quirks. Eagle-eyed observers will notice there is a
setTimeout() before the execution of the custom code begins. This is intentional – the base
insertRendering() method fires off an asynchronous jQuery animation that there’s no good way to tap into (at least that I know of) that lasts for 500ms. This
setTimeout() is to accommodate for that animation to complete. You’ll also notice there are a number of loops due to the fact that Sitecore stores the renderings for a placeholder in an array instead of a tree so each rendering in the array will need to be checked for possible instances of Vue components.
If you have a placeholder in a Vue component, Sitecore will throw an error when you add a rendering to that placeholder.
Designing, building, and implementing top-notch experiences not only requires a great deal of planning, strategy, and time – it also requires the right digital experience platform (DXP) and the right development approach for your business needs.
This is due to the fact that Sitecore uses a
key property in the placeholder
<code> tag to identify the placeholder key. It also uses this property when executing the AJAX call to insert a rendering to identify the placeholder to insert the rendering into. Vue also uses the
key property as a reserved property and takes it in as a sort of identifier for a component. When you have a placeholder in a Vue component and the Vue component is initialized, Vue sees the
key property on the placeholder
<code> element and consumes it for its purposes, then removes the property from the element. This is what causes the error – when the AJAX call to insert the rendering is called, the placeholder key value is empty and Sitecore does not know where to insert the rendering requested.
How do we solve this? Well, we can take advantage of the Vue rendering lifecycle and ensure that the
key property is reinstated on any placeholders after Vue renders the component.
- Before the Vue component renders, store the value of the placeholder key and the element’s unique ID in an array.
- Render the Vue component.
- After the Vue component renders, take each value in the array and set the value of the
keyattribute on each tracked identifier.
The solution actually went through several iterations as there were some key tenets that I wanted to meet:
- Minimally intrusive
- Don’t break Vue or Experience Editor
Thus, the Sitecore Experience Editor Vue plugin was born. The plugin ensures easy usage and reusability (
Vue.use(SitecoreExpEditorPlugin);) and the ability to use a global Vue mixin in the plugin can ensure that the logic needed before the creation and after the instantiation of a Vue component will always execute without a developer needing to remember to add in something to their Vue component.
The plugin is now published on npm! You can get it with:
npm install --save-dev vue-scexpeditor
yarn add -D vue-scexpeditor
Then, all you’ll need to do to use it is to import it and use the plugin:
import SitecoreExpEditorPlugin from 'vue-scexpeditor'; Vue.use(SitecoreExpEditorPlugin);
You can find the code for this on GitHub – https://github.com/georgechang/vue-scexpeditor