I already wrote about how designers discover the wonderful world of oop about the modular architecture of a design system, and now it's time to go into an even greater decomposition. This time I'll tell you how a micromodular approach will help you structure layouts, build an understandable documentation system and get a kind of versioning.
— , ( , ). , . , , .
, (), .
, - , , .
, . -, , , , . , , , .
, , . -, :
;
;
( );
.
. , — .
— . - . .
, , . , , - , .
:
— , , . " " , - - .
, " ", ... . , , , - . , , , , . .
, . - — .
" ", . .
— , , , - , .
. , . .
, , , , . .
, . , " " , OTP- . , - , — ( " ").
, :
, ;
;
.
, , OTP-. , , , .
, . .
— , , . - — .
, , , , . .
, , , . , .
" " . , — / . , , :) , , , .
, " " .
-, , , . , , .
, - , - .
! . . 100500 , . , . .
-.
, — , , . , , . , -, . . . — . , , , , . :(
— :
PR (Prod) —
R (hange request) —
TC (Target condition) - thoughts about what will leave in the next CR and where we are going at all.
Each version consists of the required versions of the corresponding micromodules. For example, there are 10 micromodules in a module, in the next CR changes affect only three of them, which means that the CR page will only have 3 of these micromodules.
As soon as CR is released, modules in PR are changed to actual ones, and changes for the next feature are poured into CR.
What is the result
By moving to this approach in preparing layouts, you can almost completely mow down duplication of screens, breeding chaos and inconsistency. Micromodules will significantly speed up the design of new features, if, of course, the whole team can at a higher level of abstraction.