mobrix-ui-beta v3.0.0-beta-v0.17

MoBrix-ui

Smart React components for every app, easily customizable for every purpose.

Status

:exclamation:

Note for MoBrix-ui v1 user

MoBrix-ui v2 introduces some breaking changes that makes it not compatible with older MoBrix verions (using different lib versions in parallel is possible, but can cause some unexpected errors). If you are using MoBrix 1.X.X, please read the dedicated guide, or upgrade it to v3.X.X!

Note for MoBrix-ui v2 user

MoBrix-ui v3 introduces some breaking changes that makes it not compatible with older MoBrix verions (using different lib versions in parallel is possible, but can cause some unexpected errors). If you are using MoBrix 2.X.X, please read the dedicated guide, or upgrade it to v3.X.X!

Summary

• MoBrix-ui philosophy
• Components building process
  • UI properties
  • Accessibility properties
  • CSS variables
  • Reactive components
• Getting started
  • Installation
  • Usage
• Tests
• Authors
• License

MoBrix-ui philosophy

This library is built upon few (but important) concepts:

• Small library size, to not impact on final app bundle size
• Few dependencies, to not introduce a bunch of additional packages (that could also introduce bugs or version conflicts with pre-existent packages)
• Let the user customize every part as desired, but with default values set otherwise, to make every component ready to be used without so many parameters
• Every component should be integrable into every react app, so their behaviour must be customizable too (with callbacks, for example)

The same concepts are also the base of another project I maintain, MoBrix-engine (check it out, it is also the base of MoBrix-ui guide page !)

Components building process

This library use a standardized process to build every component. As result, every component has a shared initial logic, shared CSS styles and shared properties. Some properties are shared between all components, for a smoother dev experience. In addition, this makes every single component easily re-usable.

UI properties

Accessibility properties

Some accessibility properties are shared between all components, for a better and smoother user experience, in any scenario:

CSS variables

MoBrix-ui is globally configurable, with CSS variables. By defining some specific custom CSS variables into your app css, you'll change the UI of all components:

Reactive components

Some components are designed with a specific structure, to sync their internal state with an external input value. This kind of component handle internally their actual value, using the value parameter as starting point. This let the component to be driven in 2 different way:

• Internally, Its internal value, when using the component without changing its value parameter from code

• External, passing the value parameter

So, we have 2 scenarios:

• If you change the component value using the component(without changing the value parameter), it will be updated internally.

• If you change the passed value parameter, the component will sync its value with the given one.

A clear example is the Input component. When changing the value parameter, the component will sync its actual value.

Getting started

Installation

If you want to use this library inside your project, just install it:

npm i mobrix-ui

Usage

After installation, you can use every MoBrix-ui component in your app. Run this example to see them in action:

import { Card, Container, Link } from "mobrix-ui";
import { render } from "react-dom";

render(
  <Container animated>
    <Card
      dark={true}
      body={<p>This page is entirely made with MoBrix-ui components !</p>}
      footer={
        <Link to="https://cianciarusocataldo.github.io/mobrix-ui">
          MoBrix-ui page
        </Link>
      }
    />
  </Container>,
  document.getElementById("root")
);

If you want to customize the UI globally, initialize the dedicated CSS variables:

* {
  --mobrix-ui-text-color: #f5f5f5;
  --mobrix-ui-background-color: #1b1b1b;
}

Tests

Unit tests for every component are located inside tests folder. The test script is executed with pre-defined test command:

npm run test

Authors

• Cataldo Cianciaruso

License

This project is licensed under the MIT License - see the LICENSE file for details