One of the largest challenges with learning Sitecore is learning all the terminology used within the Sitecore CMS platform. This page should be used as a guide to help understand the lingo used in the industry.
Accelerator – An accelerator in Sitecore is a setup of components that are built to allow the content editor to get up to speed faster and in some cases will allow the content editor to create content for their website without a developers intervention. Some current popular Accelerators include SxA and BrainJocks Score.
Bucket – A bucket in Sitecore is a folder that is made up other folders which are created automatically based on rule conditions and actions. Typically these rules are the default rules that Sitecore comes with out of the box, but in some instances these rules can be customized.
Content Editor – This is one of two interfaces in sitecore really meant for more experienced Sitecore users. The other interface is the Experience Editor (v. 8) previously known as the page editor (before v. 8). It consists of a tree of items along the left hand side of the screen, and an area to edit fields along the right hand side of the screen. Along the top, consists of menus that consist of groupings called chunks, of commands.
Controller Rendering – Pertains directly to MVC within Sitecore. This is a special type of layout item, that defines a controller and an action for a rendering (also known as a component).
Contact – Coming Soon
Datasource – This is where the magic happens in Sitecore. A data source is a special kind of field, that can be assigned with predefined or in some cases undefined types of items. Example: You could have a rendering or sublayout that pull in by default the most recent article, however it could also be customized by a data source that for this rendering or sublayout would take a type of article. Once this data source is set to an article, it will pull that item instead of the default logic of pulling the most recent article. Where this becomes very powerful, is that you could then define personalization rules on this component, which influences what data source to use for the rendering. So for example, a personalization rule could determine that if the current user is located in the US, it would pull an article about something happening in the US, whereas someone coming from Europe might see a completely different type of article.
Dictionary – This is a Key/Phrase used to provide localization of text of short phrases on the site. Example, you would use this type of item, if you had a search box on your homepage, and the button for the form says “Go”, you would create a new dictionary item called “Go”, and then you would pull this dictionary item from your renderings. If then you were using the rendering on a separate language version of the site, for example Spanish, you could then define a separate version of the dictionary item and set it’s Phrase too the Spanish translation of “Go”.
Dictionary Domain – Is a folder that contains dictionary definitions. Domain dictionaries as I mentioned previous in this article, are a great way to define dictionary items for either your content tree or for your website. If you have multiple websites, you can use dictionary domains to separate the dictionary items for each site/tenant.
Engagement Plan – Coming Soon
Experience Editor – The is one of the two primary interfaces for editing content in the Shell of Sitecore. Unlike the Content Editor which can be difficult to use and understand where all the data for one specific page lives within the content tree, the Experience Editor, displays the full assembled page to the content editor, in which they work with UI elements to make working with the page and it’s complex datasources a breeze.
Fast Query – This is a special type of query in Sitecore, which as it’s name implies, is faster than Sitecore Query, which searches the content tree recursively until it finds the results. Typically fast query is ideal for searching Sitecore when there are more than 100 items, but up to 1000 items. After that Lucene Query would be the better option. Fast query returns results in no specific order, which unlike Sitecore Query, which would return them according to their Sitecore order.
Field – This is a building block of Sitecore. A field defines specific data types that can be stored for an Item Template in Sitecore. Technically a field is also an Item, and Items make up everything in Sitecore.
Glass – Coming Soon
Goal – Coming Soon
Helix – This is a design guideline on how you should build your Sitecore sites. This is a recommendation from the Sitecore organization, but it does not define your technical architecture when using Helix. At its core, Helix defines that everything should be developed to be modular, and it’s important to focus on the module’s dependencies with a goal towards reducing the testing needed when changes are made to one of the modules. The structure is setup in a Foundation, Feature and Project setup.
Index – Coming Soon
Item – An item is another basic building block of Sitecore, everything you see in the content editor, is an Item within sitecore. Some items can be used to describe other items within Sitecore, such as a Template Item.
Item Template (Refer to Template)
Layout – First this is a major portion of the Content Tree. In the Layout portion, there is definition items for how the presentation of the front end of the website will appear to the website visitor.
Lucene – Coming Soon
Master – Coming Soon
Personalization – Coming Soon
Pipeline – Coming Soon
PLD – This is an acronym, one which you will see often times in my blog. It stands for Presentation > Layout > Design, and it just describes where the interface is. So if you click the on Presentation Tab, then locate the Layout Chunk, and then click on the Design button, you will be presented with Layout details that define how that item will be displayed to the user in their browser.
Processor – Coming Soon
Profile Cards – Coming Soon
Rendering – Coming Soon
Role – Coming Soon
Shared Fields – Coming Soon
Sitecore Query – Coming Soon
Standard Fields – Coming Soon
Standard Values – Coming Soon
Sublayout – Coming Soon
Synthesis – Coming Soon
TDS – Coming Soon
Template – Coming Soon
Un-Versioned Fields – Coming Soon
Unicorn – Coming Soon
Version – Coming Soon
Version Fields – This is the default type of field in Sitecore, which pretty much means that for every language and version of languages, there will be a separate value for this field.
Workflow – Coming Soon
XDb – Coming Soon