feat(MDS): Button component

[LagunaElectric]

Component: Button

Feature Request: The Button component is needed to provide users with interactive elements that trigger actions or perform specific functions within the application. It serves as a primary element for user interaction and engagement.

Reasons for the Component:

• User Actions and Interactions: Buttons enable users to perform actions, submit forms, navigate through the application, or trigger specific functionality, making them a fundamental element for user interaction.
• Visual Feedback and Call-to-Action: Buttons provide visual feedback when interacted with, giving users a clear indication that an action has been triggered or is in progress. They also serve as call-to-action elements, guiding users towards important actions or next steps.
• Consistent Design Language: Incorporating a standardized Button component ensures a consistent design language and user experience throughout the application, promoting usability and familiarity.

Variations and Special Options: The Button component should support the following variations and special options:

• Button Types: Include variations such as primary, secondary, outline, text, icon-only, or any other desired styles to accommodate different design needs and emphasize specific actions.
• Sizes: Provide options for different button sizes, allowing flexibility in visual hierarchy and accommodating various content or design requirements.
• Disabled State: Support a disabled state for buttons that should not be interactable, indicating that the associated action is currently unavailable or not applicable.
• Loading State: Include an option to display a loading indicator within the button to provide feedback when an action is in progress or requires additional time.
• Customization: Allow for customization of button styles, such as color, border, typography, and hover/focus effects, to align with the overall design system or specific branding requirements.