---
schema_version: "1"
id: bd231a3f42e29278da04489d1cf8a72f89076dfcc36559a374385f6c1de1e55f
title: Lightning Types Glossary of Terms
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/lightning-type-systems/lightning-types/references/lightning-types-glossary.md
canonical_url: https://developer.salesforce.com/docs/platform/lightning-types/references/lightning-types/lightning-types-glossary.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 327a957d502964ffe37b8226d9b1afcea9e12e768e8de273849114a288bdc244
products:
  - Lightning Types Developer Guide
  - lightning-type-systems
---
# Lightning Types Glossary of Terms

Learn more about the terms used in Lightning Types at Salesforce.

## Apex Class

A template or blueprint for creating Apex objects. Use an Apex class to define the data structure (schema) for Custom Lightning Types.

## Channel

A specific context or connection, such as `lightningDesktopGenAi` for the Agentforce panel, where you can override a custom Lightning type’s connections and the default UI. Different channels can have different `editor.json` and `renderer.json` configurations within the Lightning Type Bundle.

## Collection Renderer

A specific type of renderer defined within `renderer.json` that uses the collection keyword to customize the display of a structured list or array of data.

## Custom Lightning Type

A developer-created, JSON-based data type used to define a custom structure, validation, and user interface (UI) for complex data in Agentforce and other Salesforce applications.

## Editor

The part of a Lightning Type that defines input UI components used to enter or edit data. In a Custom Lightning Type bundle, this configuration resides in `editor.json`.

## Fully Qualified Name (FQN)

A unique name that identifies a metadata component, often by combining a namespace with the component’s developer name. For example, the `lightning:type` keyword in `schema.json` uses an FQN to reference an Apex class, such as `@apexClassType/c__AvailableFlight`.

## JSON Schema

A standard specification used to define the structure, constraints, and validation rules for JSON data. The `schema.json` file in a Lightning Type Bundle uses this specification.

## Keyword

A reserved term in a `schema.json` file that defines a specific aspect of the data’s structure or validation rules. For example, `title`, `properties`, and `lightning:type` are keywords.

## Lightning Type

A JSON Schema-based data type used to structure, validate, and display data, consisting of a schema, an optional editor, and an optional renderer. Lightning Types include Standard Lightning Types and Custom Lightning Types.

See [Standard Lightning Types](https://developer.salesforce.com/docs/platform/lightning-types/guide/lightning-types.html#standard-lightning-types) and [Custom Lightning Types](https://developer.salesforce.com/docs/platform/lightning-types/guide/lightning-types.html#custom-lightning-types).

## Lightning Type Bundle

The metadata component, with the API name LightningTypeBundle, used to create and deploy Custom Lightning Types. It’s stored in the lightningTypes folder and contains the `schema.json` file and, optionally, channel-specific folders with `editor.json` and `renderer.json` files.

## Lightning Web Component (LWC)

A UI framework built on standard HTML, JavaScript, and CSS for creating custom user interface components on the Salesforce platform. Use LWCs to define the custom Editor and Renderer for Custom Lightning Types.

## Metadata API

A Salesforce API used for retrieving, deploying, creating, updating, or deleting customization information, such as Custom Lightning Type Bundles.

## Namespace

A unique identifier used to distinguish metadata components. Use the default `c` namespace for components created in your org, or use the package’s namespace—for example, `isv`—for components from a managed package.

## Renderer

The part of a Lightning Type that defines the output UI component used to display data. In a Custom Lightning Type bundle, this configuration resides in `renderer.json`.

## Schema

The part of a Lightning Type that defines the data’s structure and validation rules by using the JSON Schema specification. In a Custom Lightning Type bundle, this configuration resides in `schema.json`.

## Standard Lightning Type

An out-of-the-box Lightning Type provided by Salesforce that includes a default schema, editor, and renderer. For example, lightning\_\_textType and lightning\_\_booleanType are standard Lightning types.