Skip to content
Motif UI
Go Pro

Attribution policy

Credit is not a favour. It is the licence.

Two licences run through this catalog, and they ask for different things. This page is the one place that spells out both, what we ask for on top of the legal minimum, and exactly what we do when a credit goes missing.

Plain-language summary written by the people who ship the catalog. It is not legal advice — for a commercial decision, read the licences themselves and talk to your own lawyer.

Assets — MIT

  • You may use, modify, ship and sell work built from an asset, including in closed-source products.
  • The licence text must travel with the code — keep the copyright notice in the file you receive.
  • You are not required to display a credit in your interface. We would like one, but it is not a condition.
  • You may not re-licence the catalog itself or publish it as your own library.

Guides — CC BY 4.0

  • You may quote, translate, remix and republish guides, including commercially.
  • Attribution is required: name Motif UI, link to the original guide, and note if you changed it.
  • Translations are a remix — credit the original and say that it is a translation.
  • You may not add a licence restriction of your own to a republished guide.

How we credit a remix

  1. The original keeps its name and its page. A remix links back to the asset or prompt it came from, and that link is not removable by us or by the remixer.
  2. The remixer is named for what they changed. Credits read “original by Motif Studio, remix by @handle” — one line, both names, no ranking of who did more.
  3. The change log is public. A published remix lists what changed in plain language, which is the part a reader actually needs to decide whether to use it.
  4. No credit on a submission that has not passed the gates. An entry that failed lint or safety is not published under anyone's name, because a public credit is also a public endorsement.

When a credit is missing

1. Tell us

The fastest route is a review note on the asset with the specific claim, or a request on the board. A link and a sentence is enough — no form, no account.

2. We check the record

Every catalog item stores its author, version and first publication date, so “who wrote this” is a lookup, not an argument.

3. We fix it in public

Corrections appear in the changelog with the entry that was wrong. Quiet edits to attribution are worse than the error, because they hide that an error happened.

4. If it is our mistake, we say so by name

“We credited the wrong author on this component and have corrected it” — not “attribution was updated”.

What we ask for beyond the licence

MIT does not require a visible credit, and we still ask for one where it is cheap: a line in a README, a mention in a launch post, a link from the footer of the thing you built. Attribution is not just compliance — it is how a reader finds the original and sees the audit scores before they copy it. Asking is not demanding, and nothing in this catalog is gated on it.

Conversely, we will not strip a remixer's name to simplify a page, and we will not aggregate contributions into an anonymous “community” credit. If a person did the work, their handle is on it.