Designing A Hierarchical Frontend Component System
Designing a frontend component system: Components (Controls, Widgets, Pages), Data Perspective (Views, Fields) & Context. Separating concerns, single responsibility principle & modular architecture for scalable UI development.
In my other series of articles, I mentioned that - In software engineering, a "component" generally refers to a reusable block of software, akin to the "building blocks" used in manufacturing. This is a fairly broad concept; it can be a software package, a web service, or a module, etc. However, in the realm of frontend development, a "component" typically refers to a view unit on a webpage, that is, a "UI component". It can be said that a "UI component" is a subset of a "component". You might also often hear the term "control". Don't worry, don't scratch your head; it's just another name...