The products we design are always influenced by the users’ world where they are situated. By bringing context into design systems first, before building the components which result from it, we enable teams to make more confident decisions and deliver the best outcomes for their users.
This is a great article. Components in a design system don’t exist in a vacuum; they exist in the context of applications that serve real people in real environments.
A core part of atomic design has always been about connecting the dots between low-level components and pages of the software applications they power. In our experience, we’ve used the design system’s reference site to capture specific applications of a given component to help provide context and additional considerations when reaching for a given component.