Design System & Token Support for Team Consistency

Feature Request: Design System & Token Support for Team Consistency

Summary:
As our team and product catalog have grown, we’ve run into significant consistency and scalability issues in Replo. We’d like to request a Design System or Token Management feature that allows teams to maintain visual consistency and streamline updates across multiple pages, components, and collaborators.

Problem Context

Our workflow involves multiple team members—designers, ecommerce specialists, and marketers—working simultaneously across various product landing pages. Replo’s current component system and styling setup make it difficult to maintain alignment when:

• Multiple contributors are building pages independently

• Visual changes (like color, typography, or spacing) need to be propagated across many files

• Reusable components are duplicated and edited manually

This results in:

• Numerous near-identical versions of key sections (like buyboxes or CTAs)

• Inconsistent colors, spacing, and breakpoints

• Excessive time spent hunting through nested containers to make basic visual updates

Feature Proposal

Introduce a Design System Layer that enables:

1. Global Design Tokens:
   Define reusable variables for core styles (colors, type, spacing, shadows, breakpoints) that can be applied consistently across projects.

   • Example: --color-primary, --radius-md, --spacing-xl

   • Updating a token updates all linked elements across files.

2. Master Components with Inheritance:
   Similar to Figma or Webflow Symbols, allow teams to maintain a master version of a section or component. Updates to the master propagate to all instances, while still allowing localized overrides (e.g., text or image changes).

3. Shared Library or Workspace Components:
   Enable teams to host a shared component library (for buyboxes, product cards, pricing tables) that can be imported into any Replo page.

   • Include version control or at least a “Last Updated” label for transparency.

4. Style Enforcement or Warnings:
   Optional setting to flag deviations from defined tokens or components to help maintain design and brand consistency.

Expected Impact

• Dramatically reduce rework and human error

• Improve visual consistency across pages and campaigns

• Allow teams to scale production without sacrificing quality

• Enable designers to define systems once and empower others to build confidently

Closing Thoughts

Replo is a powerful tool for fast page iteration, but as teams and complexity grow, the lack of design system infrastructure becomes a serious bottleneck. Adding token and library support would make Replo exponentially more powerful for cross-functional teams and larger ecommerce organizations.