Lightning Components Developer Guide
Summer '26 (API version 67.0)
Spring '26 (API version 66.0)
Winter '26 (API version 65.0)
Summer '25 (API version 64.0)
Spring '25 (API version 63.0)
Winter '25 (API version 62.0)
Summer '24 (API version 61.0)
Spring '24 (API version 60.0)
Winter '24 (API version 59.0)
Summer '23 (API version 58.0)
Spring '23 (API version 57.0)
Winter '23 (API version 56.0)
Summer '22 (API version 55.0)
Spring '22 (API version 54.0)
Winter '22 (API version 53.0)
Summer '21 (API version 52.0)
Spring '21 (API version 51.0)
Winter '21 (API version 50.0)
Summer '20 (API version 49.0)
Spring '20 (API version 48.0)
Winter '20 (API version 47.0)
Summer '19 (API version 46.0)
Spring '19 (API version 45.0)
Winter '19 (API version 44.0)
Summer '18 (API version 43.0)
Spring '18 (API version 42.0)
Winter '18 (API version 41.0)
Summer '17 (API version 40.0)
Spring '17 (API version 39.0)
Winter '17 (API version 38.0)
Summer '16 (API version 37.0)
Spring '16 (API version 36.0)
Winter '16 (API version 35.0)
Summer '15 (API version 34.0)
Spring '15 (API version 33.0)
Winter '15 (API version 32.0)
Configure Components for Lightning Pages and the Lightning App Builder
Lightning Component Bundle Design Resources
Configure Components for Lightning Experience Record Pages
Create Dynamic Picklists for Your Custom Components
Tips and Considerations for Configuring Components for Lightning Pages and the Lightning App Builder
Add Components to Apps
Use Lightning Components in Visualforce Pages
Newer Version Available
Get Your Lightning Components Ready to Use on Lightning Pages
Custom Lightning components
don’t work on Lightning Pages or in the
Lightning App Builder right out of the
box. To use a custom component in either of these places, you must configure the component and its
component bundle so that they’re compatible.
-
Configure Components for Lightning Pages and the Lightning App Builder
There are three steps you must take before you can use your custom Lightning components in either Lightning Pages or the Lightning App Builder. -
Lightning Component Bundle Design Resources
Use a design resource to control which attributes are exposed to the Lightning App Builder. A design resource lives in the same folder as your .cmp resource, and describes the design-time behavior of the Lightning component—information that visual tools need to allow adding the component to a page or app. -
Configure Components for Lightning Experience Record Pages
After your component is set up to work on Lightning Pages and in the Lightning App Builder, use these guidelines to configure the component so it works on record pages in Lightning Experience. -
Create Components for Lightning for Outlook and Lightning for Gmail (Beta)
Create custom Lightning components that are available for drag-and-drop in the Email Application Pane for Lightning for Outlook and Lightning for Gmail (Beta). -
Create Dynamic Picklists for Your Custom Components
You can expose a component property as a picklist when the component is configured in the Lightning App Builder. The picklist’s values are provided by an Apex class that you create. -
Tips and Considerations for Configuring Components for Lightning Pages and the Lightning App Builder
Keep these guidelines in mind when creating components and component bundles for Lightning Pages and the Lightning App Builder.