Borders

Borders can be used to break up sections of content, or to separate content that might have different purposes or meaning

Overview

Borders can be used to delineate spaces, emphasize elements, and increase clarity in content-dense UI. Proper use of borders helps in creating a visual heirarchy, seperating content, and drawing marketer's attention to specific sections of the page.

Borders also can include rounded edges that help modernize the interface and align with Iterable's brand identity.

 

Border width

  • 1px (default) - used in most applications like card borders, dividing Action Menu items, and seperating a header from the content
  • 2px - can be used to draw emphasis to an input or a container that is actively being edited, like the Details of a campaign or template.
1px
borderWidth-1
The default border width and should be used in almost all cases.
2px
borderWidth-2
Used to indicate an input field has an error, or that an interace element is currently being edited—like the Details card in templates
4px
borderWidth-4
Special circumstance sonly, can be used to highlight an active tab

 

Border color

Primary

This is the default color style for borders in Aurora.

It can be quickly applied in the Stroke property using the --border-primary variable.

 

Ref to 29996:248370

Ref to 29996:248370

 

Subtle

Use a 1px subtle border to break up sections of content or actions, for example separating additive actions from destructive actions in a menu.

It can be quickly applied in the Stroke property using the --border-subtle variable.

 

Ref to 29996:248365

Ref to 29996:248365

 

Semantic borders

Some elements can have semantic meaning based on their style. This follows the same patterns outlined in the “Applying Color” document. The different semantic borders are outlined in the palette below.

 

#b56dc6
interactive
#ebd3f1
interactive-subtle
#6a266d
interactive-strong
#bf3144
destructive
#fbc3cb
destructive-subtle
#0e9976
success
#caf3e7
success-subtle
#bd5b00
warning
#ffdad3
warning-subtle
#2489a9
info
#c2f0fc
info-subtle

 

Subtle semantic borders

When deciding between whether to use the base or subtle variable, it’s important to consider the element that it’s being applied to. For instance, a component may use a subtle border to help prevent the background of the component from bleeding into the background of the page (particularly on grey).

 

Ref to 29996:249946

Ref to 29996:249946

 

Strong semantic borders

Some semantic borders have a “strong” variable that is used in input controls that have more emphasis and can communicate affordance to the marketer on the component’s state—error, selected, success, etc.

 

Ref to 30892:322278

Ref to 30892:322278

Border radius

Border radius can soften the look of elements and align with Iterable's brand style. Most border radii is defined at the component level, but may need to be applied to unique containers or domain-specific elements.

 

Ref to 30906:332791

Ref to 30906:332791

 

0px
0px
borderRadius-none
Can be applied to quickly override the border radius of a component to 0
2px
2px
borderRadius-sm
Used to the soften the edges of smaller UI elements (16px or smaller) to prevent them from looking full rounded
4px
4px
borderRadius-md
The default border radius for most components and interface elements
6px
6px
borderRadius-lg
Used in floating elements like Action Menus, select dropdowns, and popovers
8px
8px
borderRadius-xl
Used in larger floating elements like modals or slideovers
12px
12px
borderRadius-xxl
Limited use currently, but should be reserved for large containers that take up a significant portion of the page
1000px
1000px
borderRadius-full
Fully rounded border radius, creates a "pill-like" shape

 

Focus rings

Focus rings indicate the actively focused element in the interface, particularly when the marketer relies on the keyboard for navigation. Focus rings play a vital role in accessibility by helping users understand where they are on a page without relying on a mouse.

 

Ref to 30906:332859

Ref to 30906:332859

 

In most cases, the focus rings are applied as predefined box-shadow configurations, but if the element is already using the box-shadow CSS property, they can be applied as outline as well.

Much like color and borders, the focus styles applied should correspond to their implied semantic meaning.

focus / warning
default
simple
focus / success
simple
default
focus / destruction
simple
default
focus / primary
default
simple
focus / info
default
simple
focus / neutral
simple
default

 

When to use borders over depth?

  • Borders are used to break up content, whereas depth can highlight areas of interest on an interface. Learn more on applying depth with shadows in Aurora.
  • A card or container that sits on the root background of the page should have depth applied and not use a border. If there are nested cards or container within that, a border should be used.