Glossary

This list includes terms commonly used in the Optimizely Content Management System (SaaS) and throughout the platform.

• access rights – Controls what a visitor can view and what an editor can do to content on an application; access rights include Read, Create, Change, Delete, Publish, and Administer. See Access rights.
• ACL – Stands for "access control list". Optimizely user permissions to access system processes and operations. For example, permissions determine who can read, change, or publish a page in a node on the tree structure.
• administrator page – Where administrators manage access rights, application languages, scheduled jobs, export and import of data between applications, and configure new applications in a multi-site solution. 
• All properties editing view – Where you access and edit properties for content. See All Properties editing view.
• API – Stands for "application programming interface". The API specifies how some software components should interact with each other, such as accessing a database or computer hardware or easing the work of programming graphical user interface components. APIs often are in the form of a library that includes specifications for routines, data structures, object classes, and variables. See Introduction to the CMS (SaaS) REST API.
• application – A distinct instance that lets you manage multiple projects or websites within the same CMS (SaaS) environment. Found in Settings. Applications let you choose which URLs to use, which languages to use, which content is shared, and much more. See Applications.
• approval sequence – Defines the steps and reviewers needed to review and approve content or certain changes (such as changes to access rights, language settings, and so on). See Approval sequences.
• asset – Content such as documents, videos, and images that can be linked to other content such as pages, blocks, elements, and experiences. See Assets.
• assets panel – Customizable placeholder for assets, where you can drag and drop images, blocks, files, or products into a CMS (SaaS) page and see non-visible settings for the content. See User interface elements.
• Autosave – Saves the page every minute by default, ensuring your work will not disappear if a sudden crash of the system or browser occurs. Your organization might have other configured settings for autosave.
• BLOB – Stands for "Binary Large Object". A BLOB provider is a framework designed to store large amounts of binary data in a more optimized and cost-effective solution, such as cloud storage, instead of in a database. Used for the asset system in CMS (SaaS).
• block – Shared, reusable content, such as an image banner, a page listing, or a video, that you can insert into one or more pages. If you edit a block's content, it updates every page on which it was inserted.  See Blocks.
• block type – A type of block, such as campaign teasers and banners, videos, news feeds, and contact forms. A block type contains a set of properties, a visual representation, and editing capabilities. It has no URL.
• Blueprint – Visual Builder blueprints are reusable layout templates that editors can create directly in the UI. You can save sections and experiences as blueprints. See Save as blueprint.
• breadcrumb – The path to the current page within the application structure. Breadcrumbs are clickable for backtracking.
• category – For Change Logs, the type of change you want to create the change log for.
• CMS – Stands for Content Management System. A software application that helps users create, edit, organize, and publish digital content.
• content area – Stores a collection of content area items (blocks or pages), letting editors manage order, group, and display of different pieces of content.
• content type – CMS (SaaS) content types include Experience, Section, Element, Page, and Block types, and Media types such as Images, Video, and Media. See Content types.
• CSS – Stands for Cascading Style Sheet. A file type that defines the appearance and layout of the application, containing fonts, colors, and so on. CSS files separate the layout of application content from the content itself, making it easier to make layout changes on an application.
• Dashboard – The CMS (SaaS) Dashboard is an overview page where editors can add gadgets or manage and monitor application activities. See Get started with CMS (SaaS).
• developer – Writes code to implement some features of the application.
• environment – Another term for instance. An individual instance of CMS (SaaS). See instance for information. 
• element – Visual Builder elements are the building blocks for creating content. Elements can be as simple as a heading with a single text input field or more complex, like a testimonial element with various optional and required fields. Elements do not have a layout. See Elements in Visual Builder. 
• experience – Visual Builder experiences are flexible and composable web or application pages that display in a list. They are comprised of sections that you can save as reusable blueprints. See Create an experience from scratch and Create an experience from a blueprint. From a developer's perspective, experiences give you access to the Layout System and UnstructuredData.
• external link – A link from one application to another application on a different domain, usually set to open in a different tab or window.
• gadget – A small application component responsible for its rendering and behavior, accessible from the dashboard or the panels in the CMS (SaaS) UI. See Gadgets.
• GDPR – Stands for General Data Protection Regulation.
• global navigation bar  – Group of options in the uppermost part of the user interface when logged in. Lets you switch between Optimizely products. See User interface elements.
• globalization – Managing content in multiple languages and localizing the user interface.
• GUID – Stands for globally unique identifier.
• Headless – Refers to a system architecture where the back end and front end of an application are separated. CMS (SaaS) is a headless content management system (CMS).
• internal link – A web page link to another page on the application.
• instance – An individual environment of CMS (SaaS). CMS (SaaS) comes with three instances. Use these instances to separate your production and non-production data. How you use your instances is up to you. See Configure environments.
• JSON – Stands for JavaScript Object Notation. It is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate.
• landing page – A target page on which a visitor "lands" after clicking a banner or link. Usually, a landing page is a web page that is separate from the main page, with the goal of the visitor performing a certain action (conversion).
• master language – The language in which the first version of content is created. See Languages.
• media – Files such as an image, a PDF, a Word document, a video, or an MP3 file. See Media.
• metadata – Information about information. For example, the meta-descriptions for content picked up by search engines or metadata for media, such as images or documents. 
• navigation panel – Contains the page tree structure, language branches, tasks, and project items of the application.  See User interface elements.
• occasional editor – An individual who occasionally changes web page content. Typically, an occasional editor lacks access rights to publish information, which a full-time editor or webmaster must carry out.
• operation – An operation is the unit of an API method and an API endpoint. For example: GET https://example.com/_cms/preview2/changesets. See Introduction to the CMS (SaaS) REST API.
• outline – A Visual Builder outline is a list view of your sections. You can drag and drop a section in any order or go to the content you want to edit by hovering over the section in the preview or the outline. See Outline.
• page type – Used by editors when creating content, contains a set of fields (properties) such as page title and main body. See Create a page.
• PDP – Stands for product display page. A commercial page that displays products for sale.
• properties –Individual fields or attributes that define the data structure of content types. They specify the type of data that can be stored and how it should be managed. Property types are the building blocks of content types. See Properties.
• rich-text editor – Utility for editing content of web pages. See Edit content using the TinyMCE rich-text editor.
• root – The parent of all folders in a file system. (Despite being called the root, it is generally found at the top of the structure).
• SaaS – Stands for Software as a Service. SaaS is a cloud-based model that lets users access software applications over the Internet. 
• search phrase – One or more words a user enters into a search box to begin a search. See Find content.
• section – Visual Builder sections are horizontal slices of a page comprised of elements. Sections use rows and columns in a grid layout to structure content. You can save sections as a reusable blueprint. See Section.
• SEO – Stands for search engine optimization. Making application content attractive to application visitors and, as a result, achieving high rankings in search results. See Search engine optimization.
• SEO URL – Corresponds to a simple address in CMS. Depending on the site set up, it may be used instead of the hierarchical URL when links are rendered in outgoing responses. The site responds to the SEO URL for incoming requests, regardless of settings.
• style – Visual Builder style settings let you modify the appearance of the content based on pre-approved guidelines. You can apply style to any level of Visual Builder content such as elements, rows and columns, sections, or experiences. See Select styles.
• URL – Stands for Uniform Resource Locator. Also known as a web address such as http://world.optimizely.com.
• user – Logs into an application to manage and administer content and products. Types of users include administrators, editors, marketers, and merchandisers. 
• visitor – Someone who visits an application using a web browser. In most cases, a visitor can use public functions and services but cannot create content and has limited access to community content. 
• Webhook – HTTP callback for sending event data in real-time.
• WYSIWYG – Stands for what you see is what you get.
• XML – Stands for extensible markup language. An open international standard for structuring and transferring data between systems.