Proposal - React Components Design System

What is the need / problem ?

The team has the intention to move from Angular to React for the Web front-end client. This is the best initial step to reduce the implementation time and a way to develop a better and robust Design System that can support better maintainability and next features.

Who does it impact ?

This is components would become the building blocks for the future versions of the OFN Web Front-End, if the initiative to migrate to React becomes a reality

What is the current impact of the problem ?

This is an opportunity to solve the problem with the UI that is implemented in Angular and not very extensible/composable and very costly to upgrade. Moving the UI to React would make the application faster, more stable and maintainable.

What is the benefit of focusing on this ?

OFN needs a Design system and a React Components Library to support the next phase of the OFN Web Client, focusing on this issue would help that the transition is faster making it less expensive.

Potential solutions that will solve the problem ?

The best option is to host the Design System in a separate repository and export it as a node module that can be consumed by the main React App.
The best known framework to test, verify and document React Design Systems is Storybook. We could use this for exporting the React System and for development and export the React Components as a node package as mentioned earlier.

Selection of a feature candidate

[value x ease matric if needed]

T-shirt size of our selected feature candidate


Metrics to measure if need is satisfied after feature is implemented

Implementation of the 20 basic components using the current design guidelines.

Feature owners

I can volunteer to spearhead this initiative.

Epic/projet where you can follow implementation

FE Upgrade.

Connected wishlist and discovery discussions*

PS: If this is not the right place or the correct way to propose this, please let me know.
Have a great day!

1 Like