Mirakl Design
Mirakl Design
  • Getting started
    • Welcome to Roma
      • Design principles
  • Design
    • Components
      • Actions
        • Action menu
        • Buttons
        • Button group
        • File download
        • Save bar
        • Tasklist
        • Contextual Toolbar
      • Datalist
      • Datatable
      • Feedback
        • Alerts
        • Activity Loader
        • Badge (status)
        • Empty state
        • Snackbar
      • Form
        • Fields
        • Pickers
        • Selection controls
        • Tree
      • Images
        • Illustrations
        • Icons
        • Media
      • Navigation
        • Hyperlink
        • Page title
        • Sidebar
        • Top bar
      • Overlays
        • Modal
        • Popover
        • Tooltip
        • Side Drawer
      • Structure
        • Global layout
        • Panel
          • Activable Panel
          • Clickable Panel
          • Expandable Panel
          • Panel tabs
          • Totalizer Panel
        • Card
    • Patterns
      • Advanced selection
      • Configure options
      • Displaying data
      • Displaying history
      • Errors
      • Forms
        • Form - Creation mode
        • Form - Edition mode
        • Form - In a modal
        • Error Management
        • Stepper form
        • Onboarding form
      • Loading
      • Progressive disclosure
  • content
    • Writing for Mirakl
      • Grammar and formatting
    • Vocabulary
      • Mirakl products
      • Which verb to use
Powered by GitBook
On this page
  • Overview
  • Guidelines
  • How to use
  • Key takeaways

Was this helpful?

  1. Design
  2. Components
  3. Actions

Save bar

A Save Bar is an action bar that sticks to the bottom of the viewport as you scroll. It contains actions related to a page and allow users to scroll without loosing visibility on the different actions

Last updated 1 year ago

Was this helpful?

Overview

Save Bar is always located at the bottom of the screen and stays fixed as you scroll through the page. It appears after a user performs an action (edit a form, tick a checkbox, etc.) from the bottom and should persist until the task is submitted or canceled.

Sticky Save should be used to save or discard in-progress changes. It contains a Button Group with a Save button as a primary action and a cancel button.

Sticky save should be used on all forms and is visible when there are unsaved changes.

To limit the user's mental load, we restrict Save Bar actions to two Buttons : "Save" (as a Primary Button) and "Cancel" (as a Secondary Button).

Sometimes, we may want to offer users a third option: "Save as draft". As this option isn't prevalent in all of our forms, we decided to introduce a specific pattern with "Save" as a Primary Split Button and "Save as draft" as a Split option.

Guidelines

How to use

Save Bar behavior is automated by Roma; it will always stick to the bottom of the page and allow the user to scroll down the page.

The Save Bar has been created to be visible enough for users to notice it without disturbing them to perform their actions.

Key takeaways

  • Align Save Bar buttons with page content

  • Respect Button content guidelines

  • Do not show Save Bar if no actions are required from users

  • Do not display more than 2 actions in the Save Bar

Learn more on how to use Save Bar in a form, depending on the form mode (creation or edition)