Landing Page Card
Design System - Landing Page component
The Landing Page Card component serves as a navigational entry point, combining visual elements, summary data, and contextual menus. Built on principles of clarity, responsiveness, and customizability, this component helps users explore modules efficiently while displaying key actions and metrics upfront.
// Sample code
<CheckBox
label="Label"
onChange={(e)=>{console.log(e.target.checked}}
/>Anatomy
Variants
Default
Displays a card with module title, optional icon, metrics, and a list of menu actions. It supports responsiveness across desktop, tablet, and mobile viewports.
Properties
Icon Supports both filled and unfilled icon styles, customizable based on visual priority or branding needs.
Icon Alignment Icons can be aligned either on the left (standard) or right (for visual distinction or emphasis).
Metrics Cards can optionally show numerical data summaries to give quick insights.
Custom Content Custom text or widgets (like contextual notes) can be injected into the card to enrich the layout.
Menu Items Actionable items like Create User, Edit User, or Delete User can be toggled based on user roles or module-specific permissions.
Property Configuration Table
Each design component offers a range of configurable options. These options are intentionally platform-agnostic, allowing implementations to adapt and tailor them to align with the specific requirements of the chosen framework.
icon
text
-
moduleName
text
-
moduleAlignment
yes/no
no
metrics
yes/no
no
metricAlignment
-
links
yes/no
-
className
yes/no
no
style
yes/no
no
index
number
no
hideDivider
yes/no
no
iconBg
yes/no
no
buttonSize
yes/no
no
onMetricClick
yes/no
no
centreChildren
yes/no
no
endChildren
yes/no
no
Usage Guide
Hierarchical structure
Enable tree selection for complex apps where submodules need to be grouped contextually. Don’t flatten deep hierarchies if users need to frequently access child modules—it hinders navigation efficiency.
Change log
Dec 15, 2024
v-0.0.2
This component is added to the website. This component is now individually versioned.
Design Checklist
All interactive states - Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).
Accessible use of colours - Colour is not used as the only visual means of conveying information (WCAG 2.1 1.4.1)
Accessible contrast for text - Text has a contrast ratio of at least 4.5:1 for small text and at least 3:1 for large text (WCAG 2.0 1.4.3).
Accessible contrast for UI components - Visual information required to identify components and states (except inactive components) has a contrast ratio of at least 3:1 (WCAG 2.1 1.4.11).
Keyboard interactions - Includes all interactive states that are applicable (hover, down, focus, keyboard focus, disabled).
Screen reader accessible - All content, including headings, labels, and descriptions, is meaningful, concise, contextual and accessible by screen readers.
Responsive for all breakpoints - Responsiveness for 3 breakpoints - Mobile, Tablet and Desktop
Usage guidelines - Includes a list of dos and don'ts that highlight best practices and common mistakes.
Content guidelines - Content standards and usage guidelines for writing and formatting in-product content for the component.
Defined variants and properties - Includes relevant variants and properties (style, size, orientation, optional iconography, decorative elements, selection states, error states, etc.)
Defined behaviours - Guidelines for keyboard navigation and focus, layout management (including wrapping, truncation, and overflow), animations, and user interactions.
Design Kit - Access to the design file for the component in Figma, multiple options, states, colour themes, and platform scales.
Last updated
Was this helpful?