Definitions
Activations - Activations are how people access an experience. Based on the Text Activation Keyword, the Studio automatically generates four unique activations for each experience: QR code, Text, URL, and Near-field Communication (NFC).
App Manifest - The web app manifest provides information about a web application in a JSON text file, necessary for the web app to be downloaded and be presented to the user similarly to a native mobile app (e.g., be installed on the home screen of a device, providing users with quicker access, and a richer experience). Within Lumavate, a web app manifest is configured at the Page level, under Page Settings. Studio Users set the Page Type to Home to reveal the web app manifest properties.
Command Center - The Command Center is used for distribution and version management of Pages, Features, and Component Sets. The Command Center is also where a Command Center Administrator or Collaborator can manage the account’s Subscription Plan. Command Center Administrators control user permissions for the Command Center and designate the Pages, Features, and Component Sets available to each Studio.
Components - Components are design elements such as a button, text, image, or video that are added to a Page to create the design. Components may include integrations to third-party applications, such as Calendly, Drift, or YouTube. Each Component belongs to a Component Set.
Component Sets - Component Sets are groupings of similar Components, managed in the Command Center. For example, the Data Visualization Component Set contains three Components providing Studio Users with a variety of ways to display data. Similarly, the Ionic Form Component Set contains several Components that enable Studio Users to create a wide range of forms with diverse field types.
Features - Features are often used for managing the data-driven portion of experiences, such as storing data from a form submission or integrating with a CRM. Features also can be used to integrate with third-party applications such as Twilio for sending SMS or Amazon Simple Email Service for triggering email notifications.
Lumavate Library - The Lumavate Library contains all the Features, Pages, and Component Sets available to Lumavate customers based on the customer's Subscription Plan. Command Center Administrators designate what Lumavate Library items are shared with each Studio.
Pages - Pages are technically UI containers that enable Studio Users to design the page layout. Components and Features are added to Pages. There are two types of Pages: Home and Normal. The Home Page Type lays down the web app manifest. Each experience can only have one Home Page. All other Page Types in the experience are set to Normal.
Progressive Web Apps (PWAs) - PWAs are web applications that function like a native mobile app–with integrations to phone hardware, the ability to access it via a home screen icon, and offline capabilities–but don’t require an app store download.
Properties - Properties are the areas within the Studio that can be edited by a Studio User. These include Properties, Feature Properties, Component Properties, and Page Properties. Properties often set frontend design, such as the text color, padding around a Component, or the header design. Properties also can control backend functionality, such as Alt Text and links. Lumavate’s multilingual support is also managed using Properties.
Publish - Publish means to make an experience available in production via the experience's Activations. Whether publishing an experience for the first time, or publishing edits to an experience, Studio Users must hit the Publish button for changes to appear in the live experience.
Studio - Experiences are built and managed within a Studio. A Studio resides under a Command Center. A Command Center can encompass multiple Studios. Companies often create Studios around brands, departments, or regions. Each Studio is provisioned with one domain or subdomain. All experiences created within a Studio are hosted on that domain or subdomain.