bellhop by actabl

Account Settings

Update your account information and preferences. Changes will be saved automatically.

When to use

Use containers to group related content with consistent spacing and visual boundaries.

Form Sections

Group related form fields with labels and inputs together.

Settings Panels

Organize configuration options into discrete sections.

Content Cards

Display structured content with clear boundaries and spacing.

When not to use

  • When semantic HTML elements are more appropriate (article, section, aside)
  • For components that have their own container logic (card, modal)
  • When full-bleed layouts are needed
  • For simple wrappers without semantic meaning—use div

Variants

Different configurations for various use cases.

Default

Simple container with padding and border for grouping content.

With Actions

Profile Settings

Manage your profile information and preferences.

With Footer

Payment Method

Select your preferred payment method for subscriptions.

Common Use Cases

Examples of where containers work best.

Account Settings

Group profile fields, preferences, and save buttons

Payment Forms

Organize billing information and payment details

Dashboard Sections

Separate different data or metric groups

Configuration Panels

Display system or application settings

Info Sections

Present structured information like details or summaries

Action Groups

Contain related actions or workflow steps

Best Practices

Follow these guidelines when using containers.

Do

  • Use for grouping related content logically
  • Provide clear headings for container contents
  • Keep container content focused and cohesive
  • Use footer for actions related to container content
  • Maintain consistent spacing within containers

Don't

  • Don't nest containers excessively (max 2 levels)
  • Don't overcrowd with too much content
  • Don't use for simple single elements
  • Don't mix unrelated content in one container
  • Don't omit headings when content needs context

Container Composition

Containers work well with form inputs and structured content.

User Information

Accessibility

Containers are designed to be accessible to all users.

Semantic Structure

  • Use appropriate heading levels (h2, h3) for container titles
  • Maintain logical content hierarchy
  • Use section or article tags when appropriate
  • Group related fields with fieldset for forms

Navigation

  • All interactive elements are keyboard accessible
  • Logical tab order flows through content
  • Focus indicators are visible
  • Buttons and links have clear labels

Visual Design

  • Sufficient color contrast for borders and text
  • Clear visual separation from surrounding content
  • Adequate spacing for readability
  • Responsive padding on all screen sizes

Resources

Design and development resources for the Container component.

Figma

Available
View in Figma →

Web Components/Angular

Available
View in Storybook →

React

Available
View in Storybook →