Versions Compared

Old Version 1

changes.mady.by.user GE-DevDoc-Bot

Saved on

compared with

New Version Current

changes.mady.by.user GE-DevDoc-Bot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • visibilityPolicySetId – determines the visibility of the component based on specified policy sets. For example, setting it to "adminOnlyPolicy" restricts the boardlet to users with admin privileges.
  • Figma: https://www.figma.com/design/yck1tcUXgdQ5aYX6iUAwrO/GE---Astronaut-Design-System?node-id=11550-252668&t=iosNC2AkSTGs5lMh-1
  • Live style guide: https://e1-dev.k8s.myapp.de/live-style-guide/id5/2-boardlet

Guidelines

Header / Toolbar

  • Every boardlet must always include a toolbar on the right side.
  • The toolbar can exist in two variations:
  • First actionbar – actions that affect the boardlet itself.
  • Second actionbar – actions that affect the content inside the boardlet. Always separated by a dividing line and cannot exist alone.
  • Limit toolbars to three visible actions. Additional actions must be grouped into an overflow menu under the “more” icon.
  • The “more” action is mandatory in every boardlet toolbar.

Footer

  • The footerbar always controls the workflow of the boardlet.
  • Workflow-related actions are always placed at the bottom right. Hierarchy flows from bottom right to bottom left.
  • Allowed footerbar layouts:
  • Tabs only.
  • Tabs with buttons (maximum two).
  • Buttons only (maximum two).
  • Tabs with actionbar (secondary option, e.g., kiosk mode).
  • The footerbar has a fixed height and may never be multiline.

Example styling of the Boardlet Header and Footer

Accessibility

...

Usage

  • Pick the visual emphasis that matches the page context by setting boardletType to Normal (bordered) for stronger separation or Ghost (borderless) when the Boardlet should blend into surrounding content.
  • Keep the header action area compact: place at most three immediate actions in the headerand expose the rest via the mandatory overflow by setting moreIconVisible: true.
  • Use the footer only for workflow-related actions or tabs. If there is no workflow, hide the region (showFooter: false) so the layout stays clean.

Sizing & Layout

  • Prevent clipping when content grows by enabling internal scrolling with scrollingEnabled: true; this preserves container height and reduces layout shifts.
  • Reduce visual noise by hiding unused chrome (showHeader: false, showFooter: false) instead of leaving empty regions.
  • Provide quick, recognizable affordances in the header by configuring leftIcon and/or rightIcon with symbols that match the Boardlet’s purpose (e.g., info, settings).

States & Feedback

  • Control presence of major regions at runtime with showHeader and showFooter to reflect task needs (e.g., hide footer after workflow completes).
  • Expose additional actions via overflow by toggling moreIconVisible; when true, users have a stable “more” entry point even when visible actions are limited.

Interactions & Events

  • Release resources and listeners on teardown with events.ON_DESTROY to keep the UI responsive and stable over time.
  • Provide deterministic automation hooks for QA and a11y testing with dataTestId so scripts can reliably target the Boardlet across builds.

Visibility & Authorization

  • Restrict who can see the Boardlet by supplying visibilityPolicySetId; when a user doesn’t match the policy, the component remains hidden, preventing accidental exposure of content or actions.

Content & Localization

  • Localize all user-facing copy with boardletNameTranslations and titleTranslations/title to match the user’s locale; keep labels short and specific so truncation is unlikely in tighter layout configurations.
  • Use displayName for internal structure-panel clarity without changing end-user text; this helps maintain a clean authoring experience across large boards.

Dos & Don’ts

DoDon’tArticle setting(s)
Keep header actions to ≤3 and surface the rest via overflow.Crowd the header with many icons and no overflow.Header elements[] (limit count), moreIconVisible: true
Hide the footer when no workflow actions exist.Leave an empty footer occupying space.showFooter: false
Use layout: "vertical" in the body to stack dense content for readability.Force cramped side-by-side layouts that truncate content.Body layout: "vertical"
Enable scrollingEnabled when content can exceed visible height.Allow content to clip, overlap, or push other regions unpredictably.scrollingEnabled: true
Localize the name and title for all supported locales.Hard-code English-only strings.boardletNameTranslations, titleTranslations/title

Accessibility

  • Provide localized output to assistive tech by filling boardletNameTranslations and titleTranslations/title for all supported locales.
  • Maintain predictable reading and navigation order by keeping section visibility (showHeader, showFooter) and section layout stable during interaction.
  • Ensure overflow actions remain discoverable by enabling moreIconVisible, so important commands are reachable without shrinking targets.
  • Expose dataTestId to support automated accessibility checks and regression testing.
  • Avoid using color alone to convey meaning; augment with recognizable leftIcon/rightIcon and clear titleTranslations/title text.