Lightning Components Developer’s Guide

Getting Started
Creating Components
Components
Component Markup
Component Namespace
Using the Default Namespace in Organizations with No Namespace Set
Using Your Organization’s Namespace
Using a Namespace in or from a Managed Package
Creating a Namespace in Your Organization
Namespace Usage Examples and Reference
Component Bundles
Component IDs
HTML in Components
CSS in Components
Component Attributes
Component Composition
Component Body
Component Facets
Best Practices for Conditional Markup
Using Labels
Localization
Enabling Lightning Components in Salesforce1
Adding Lightning Components to Salesforce1
Configure Components for Lightning Pages and the Lightning App Builder
Adding Components to Apps
Providing Component Documentation
Expressions
UI Components
Supporting Accessibility
Communicating with Events
Creating Apps
Debugging
Reference
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Component Namespace

Every component is part of a namespace, which is used to group related components together. If your organization has a namespace prefix set, use that namespace to access your components. Otherwise, use the default namespace to access your components.

Another component or application can reference a component by adding <myNamespace:myComponent> in its markup. For example, the helloWorld component is in the docsample namespace. Another component can reference it by adding <docsample:helloWorld /> in its markup.

Lightning components that Salesforce provides are grouped into several namespaces, such as aura, ui, and force. Components from third-party managed packages have namespaces from the providing organizations.

In your organization, you can choose to set a namespace prefix. If you do, that namespace is used for all of your Lightning components. A namespace prefix is required if you plan to offer managed packages on the AppExchange.