Skip to content

Raise a conflict

Two rules, two products, or a past decision pulling different ways? Raise it here.

Two of Syntara’s rules point different ways, a past decision doesn’t fit what you’re seeing, or two products need opposite things. Raise it here: answer a few questions, and GitHub opens with everything filled in.

What happens next

The design lead sorts it, decides within the review times, and writes the reason on the issue. Every decided conflict ends in a decision record that names who decided. How each kind is settled is on Governance.

Before you raise it

  • Two rules clash? The priority order settles it, without a debate: accessibility over not breaking consumers over brand wishes over speed.
  • Disagree with a past decision? It’s reopened only with new information — a measurement, a bug, or a need nobody knew about. Check the decision records first.
  • Two products want opposite things? Look for a prop, a variant or a brand input that serves both. A brand is data, not a fork.

Tell us what clashes

Answer here, then GitHub opens with everything filled in. Press Submit there to raise it. You need a GitHub account; nothing you type is stored on this site.

What kind of conflict is it?
Two of Syntara’s own rules point different ways. The priority order settles it.
Reopened only with new information: a measurement, a bug, or a need nobody knew about.
First we look for a prop, variant or brand input that serves both.
Raise it anyway; it gets sorted when it’s read.
One line, e.g. “Button focus ring vs Harbor’s outline style”.
Name both sides. For a rule clash, name both rules. For a past decision, link its record.
Which screen, product or brand. You can attach a screenshot on GitHub.
Opens in a new tab.