Skip to main content

Context (Contextual)

PropertyValue
descriptionContext (Contextual)
tagsref

Context defines the environment, conditions, and relationships in which something exists and is interpreted. Within MAC, it ensures that no component, piece of content, or system is treated in isolation. Everything is understood relative to its purpose, usage, and surrounding system.

While Modular and Atomic define how things are built, Contextual defines how things are understood and applied. It answers the questions that raw structure alone cannot: where something belongs, why it exists, and how it should behave in a specific situation.

Role in MAC​

Context is the layer that connects all parts of MAC into a coherent system.

  • A module without context is just a reusable piece
  • An atomic element without context is just a small unit
  • With context, both become meaningful, usable, and correctly applied

This is what prevents misuse, duplication, and inconsistent implementations.

Core Dimensions of Context​

Every element in MAC should be evaluated across these dimensions:

  • Scope - where it applies (project, system, component, global)
  • Intent - why it exists (problem it solves)
  • Relationships - how it connects to other elements
  • Constraints - limitations or rules that affect usage
  • Environment - where and how it is used (technical, business, UX)

Context in Practice​

Context is applied at multiple levels:

  • Product context - what the product is trying to achieve
  • System context - how parts interact within the system
  • Component context - where and how a component is used
  • Content context - who the information is for and why
  • Technical context - implementation details, dependencies, constraints

Each element should be understandable without relying on assumptions.

Example​

  • Without context: Use this component for displaying data.
  • With context: Use this component to display product pricing within listing cards on eCommerce pages, where real-time updates and currency formatting are required.

Principle​

Context should always be explicit and documented, not inferred.

In MAC, clarity is achieved when:

This is what turns a collection of parts into a system.