Core/Entity classes
Application and entity specific classes.
Core and entity classes provide targeted styling capabilities for the Ubidots application. They let you apply CSS customizations either globally across the platform or to specific entities. These classes are essential for creating consistent theming and entity-specific customizations without affecting other parts of the application.
Why Core/Entity Classes Matter
Global Consistency: The core-view__container class enables platform-wide styling changes that affect every view in the application, ensuring visual consistency across all entities.
Entity Isolation: Entity-specific classes like devices-view__container allow you to customize individual views without impacting other parts of the application, providing precise control over each entity's appearance.
Scalable Customization: This system supports both broad theming changes and granular entity customizations, making it easy to maintain brand consistency while accommodating specific functional requirements.
Core & Entity-specific Classes
Applied to every view container across the entire Ubidots application.
core-view__containerUse cases:
Platform-wide color schemes.
Global typography settings.
Universal spacing and layout adjustments.

Example
Applied to every entity container that's exposed in the Ubidots application. It follows the syntax:
Use cases:
Entity-specific color coding.
Custom layouts for each entity.
Entity-specific spacing and typography.

Available entity classes are:
Devices
devices-view__container
Device groups
device_groups-view__container
Dashboards
dashboards-view__container
Events
events-view__container
Event logs
events_logs-view__container
Reports
reports-view__container
Users
users-view__container
Organizations
organizations-view__container
Example
Entity banner classes
For now, only the Device entity is supported. More modules will be available soon.
These classes apply to entity table views exposed in the Ubidots application, except Dashboards. They let you add an image banner or linear gradient to the entity table.

It follows the syntax:
The layout class is only needed to hold two additional classes for the two banner options. The banner classes are:
<entity>-table__banner<entity>-table__banner-gradient
Use each one based on the banner type you want to implement.
Example
This CSS adds an image banner to the Devices view:
Rendered DOM
The rendered HTML for the Devices view, including a banner, looks like this. This example is taken directly from the application:
Last updated
Was this helpful?