It will define the color of the light based on its semantic meaning.
+
+ 'default'
+
+
size
@@ -69,15 +69,13 @@ const sections = [
},
];
-const StatusLightCodePage = () => {
- return (
-
-
-
-
-
-
- );
-};
+const StatusLightCodePage = () => (
+
+
+
+
+
+
+);
export default StatusLightCodePage;
diff --git a/apps/website/screens/components/status-light/overview/StatusLightOverviewPage.tsx b/apps/website/screens/components/status-light/overview/StatusLightOverviewPage.tsx
new file mode 100644
index 0000000000..f4976e0778
--- /dev/null
+++ b/apps/website/screens/components/status-light/overview/StatusLightOverviewPage.tsx
@@ -0,0 +1,137 @@
+import { DxcParagraph, DxcBulletedList, DxcFlex, DxcTable } from "@dxc-technology/halstack-react";
+import QuickNavContainer from "@/common/QuickNavContainer";
+import QuickNavContainerLayout from "@/common/QuickNavContainerLayout";
+import DocFooter from "@/common/DocFooter";
+import Example from "@/common/example/Example";
+import HeaderDescriptionCell from "@/common/HeaderDescriptionCell";
+import variants from "./example/variants";
+import anatomy from "./images/status_light_anatomy.png";
+import Image from "@/common/Image";
+
+const sections = [
+ {
+ title: "Introduction",
+ content: (
+
+ Being a non-clickable UI element, the status light is used to provide a quick, at-a-glance
+ indication of system states, alerts, or conditions within an interface. Designed for clarity and instant
+ recognition, it seamlessly integrates into various layouts without adding cognitive load. Status lights follow a
+ consistent color-coded system to ensure users can easily interpret their meaning. They are often used alongside
+ other components, such as tables, accordions, or dashboards, to enhance visibility and provide contextual
+ awareness.
+
+ ),
+ },
+ {
+ title: "Anatomy",
+ content: (
+ <>
+
+
+
+ Status light: the core visual element of a status light, designed as dot for clarity and
+ easy recognition.
+
+
+ Label: a short text description alongside the status light to provide additional context.
+
+
+ >
+ ),
+ },
+ {
+ title: "Variants",
+ content: (
+ <>
+
+ The status light component is available in five semantic variants, each represented by a distinct color. These
+ colors ensure clear communication of different states.
+
+
+ Additionally, the component comes in three different sizes, allowing for flexibility across various layouts
+ and screen sizes while maintaining readability and visual consistency.
+
+
+
+
+
+
Variant
+ Description
+
+
+
+
+
+ Default
+
+
For neutral statuses, like archived, draft, paused...
+
+
+
+ Info
+
+
For live statuses, like active, in use, uploaded...
+
+
+
+ Success
+
+
For positive statuses, like finished, approved, completed...
+
+
+
+ Warning
+
+
For pending or critical statuses, like scheduled, in progress, processing...
+
+
+
+ Error
+
+
For negative statuses, like incomplete, rejected, failed...
+
+
+
+ >
+ ),
+ },
+ {
+ title: "Best practices",
+ content: (
+
+
+ Ensure semantic accuracy: always match each status light color with the correct meaning to
+ maintain clarity and avoid misinterpretation.
+
+
+ Optimize for different screen sizes: Select the appropriate size to ensure visibility and
+ legibility across various layouts.
+
+
+ Use clear and concise labels: Keep them brief and ensure they accurately describe the current
+ state.
+
+
+ Combine with badges carefully: status lights and semantic badges can only be used together if
+ one of them does not use a semantic color or if their semantic colors do not contradict each other. This
+ prevents misinterpretation and maintains clarity in data visualizations such as tables, charts, or grids.
+
+
+ Use strategically: overusing status lights in interfaces with high cognitive load can
+ overwhelm users and disrupt readability. Use them only where they add real value.
+
+
+ ),
+ },
+];
+
+const StatusLightOverviewPage = () => (
+
+
+
+
+
+
+);
+
+export default StatusLightOverviewPage;
diff --git a/apps/website/screens/components/status-light/usage/example/variants.ts b/apps/website/screens/components/status-light/overview/example/variants.ts
similarity index 100%
rename from apps/website/screens/components/status-light/usage/example/variants.ts
rename to apps/website/screens/components/status-light/overview/example/variants.ts
diff --git a/apps/website/screens/components/status-light/overview/images/status_light_anatomy.png b/apps/website/screens/components/status-light/overview/images/status_light_anatomy.png
new file mode 100644
index 0000000000..e0f4fc3444
Binary files /dev/null and b/apps/website/screens/components/status-light/overview/images/status_light_anatomy.png differ
diff --git a/apps/website/screens/components/status-light/specs/StatusLightSpecsPage.tsx b/apps/website/screens/components/status-light/specs/StatusLightSpecsPage.tsx
deleted file mode 100644
index e767785daf..0000000000
--- a/apps/website/screens/components/status-light/specs/StatusLightSpecsPage.tsx
+++ /dev/null
@@ -1,52 +0,0 @@
-import { DxcBulletedList, DxcFlex, DxcParagraph } from "@dxc-technology/halstack-react";
-import Image from "@/common/Image";
-import QuickNavContainer from "@/common/QuickNavContainer";
-import QuickNavContainerLayout from "@/common/QuickNavContainerLayout";
-import Figure from "@/common/Figure";
-import DocFooter from "@/common/DocFooter";
-import specsImage from "./images/status-light_specs.jpg";
-import anatomyImage from "./images/status-light_anatomy.jpg";
-
-const sections = [
- {
- title: "Specifications",
- content: (
-
-
-
- ),
- },
- {
- title: "Anatomy",
- content: (
- <>
-
-
- Status Light
- Label
-
- >
- ),
- },
- {
- title: "Design tokens",
- content: (
- <>
- This component currently has no design tokens.
- >
- ),
- },
-];
-
-const StatusLightSpecsPage = () => {
- return (
-
-
-
-
-
-
- );
-};
-
-export default StatusLightSpecsPage;
diff --git a/apps/website/screens/components/status-light/specs/images/status-light_anatomy.jpg b/apps/website/screens/components/status-light/specs/images/status-light_anatomy.jpg
deleted file mode 100644
index 1c0f9195e6..0000000000
Binary files a/apps/website/screens/components/status-light/specs/images/status-light_anatomy.jpg and /dev/null differ
diff --git a/apps/website/screens/components/status-light/specs/images/status-light_specs.jpg b/apps/website/screens/components/status-light/specs/images/status-light_specs.jpg
deleted file mode 100644
index 42c95e4642..0000000000
Binary files a/apps/website/screens/components/status-light/specs/images/status-light_specs.jpg and /dev/null differ
diff --git a/apps/website/screens/components/status-light/usage/StatusLightUsagePage.tsx b/apps/website/screens/components/status-light/usage/StatusLightUsagePage.tsx
deleted file mode 100644
index fefd27c902..0000000000
--- a/apps/website/screens/components/status-light/usage/StatusLightUsagePage.tsx
+++ /dev/null
@@ -1,124 +0,0 @@
-import { DxcParagraph, DxcBulletedList, DxcFlex, DxcTable } from "@dxc-technology/halstack-react";
-import QuickNavContainer from "@/common/QuickNavContainer";
-import QuickNavContainerLayout from "@/common/QuickNavContainerLayout";
-import DocFooter from "@/common/DocFooter";
-import Example from "@/common/example/Example";
-import HeaderDescriptionCell from "@/common/HeaderDescriptionCell";
-import variants from "./example/variants";
-
-const sections = [
- {
- title: "Usage",
- content: (
-
- The Status light component serves as a powerful communicator of an element or process' status. It focuses
- exclusively on conveying semantic information within a range of five variants, each of them aligned with its
- specific process status.
-
- ),
- subSections: [
- {
- title: "Do's",
- content: (
-
-
- Match each status light variant with the correct semantic meaning to communicate clearly and consistently
- messages about our statuses.
-
-
- Use each size of the component according to the different screen sizes where it will be placed, paying
- special attention to maintaining legibility and functionality.
-
-
- Use concise and precise labels that reflect the status of a process accordingly. You should not use more
- than three words in a status light label.
-
-
- ),
- },
- {
- title: "Don'ts",
- content: (
-
-
- Mix semantic meanings within Status lights, as this will lead to confusion and misinterpretation of
- process states.
-
-
- Use Status light and semantic badges in the same data visualization format (tables, charts, data
- grids...).
-
-
- Overuse the component. In screens with high cognitive load, you should not overuse this component, as it
- may confuse users and interrupt the reading flow.
-
-
- ),
- },
- ],
- },
- {
- title: "Variants",
- content: (
- <>
-
- The Status light component has five different modes, each one corresponding to its semantic meaning.
-
-
-
-
-
-
Variant
- Description
-
-
-
-
-
- Default
-
-
For neutral statuses, like archived, draft, paused...
-
-
-
- Info
-
-
For live statuses, like active, in use, uploaded...
-
-
-
- Success
-
-
For positive statuses, like finished, approved, completed...
-
-
-
- Warning
-
-
For pending or critical statuses, like scheduled, in progress, processing...
-
-
-
- Error
-
-
For negative statuses, like incomplete, rejected, failed...