The current Design System pattern is based on angular
A collection of SAAS variables.
A collection of Angular components with their associated SASS stylesheet
A lot of focus was given to re-usable layouts, which i feel is useless because Safire cannot provide a universal lib that fits all business/brand's needs.
(Should drop this and only provide the layout primitives)
It was heavily driven feature modules, which was a bad idea as it imposes restrictions and becomes opinionated on how all projects should work.
Going forward, features that can be accomplished by leveraging Safire should merely be showcased as a collection of example templates(or pages), that projects can copy and paste. E.g. Login page, 404 page etc.
Existing pattern didn't have foundational implementation of components,
but rather in angular only. This gave problem when we need to use it outside angular or implement the style guide in a consistent way in another framework (or as another library. may be maintained by specific project ( child design system))