Build render variants

A render variant describes how a credential or issuer card is drawn in a wallet: colours, logo, background, or a full SVG template. Variants live in a tenant library so several designs can share one card, and a variant affects nothing until a design prefers it for a locale.

Complete first: Manage design assets.

Steps and why they come in this order

Step	Why here
1. Review the variant library	Variants are shared. Editing one changes every design that prefers it, so see what exists and who uses it first.
2. Create a card per locale	A design prefers variants by id, so each card must exist before it can be attached.
3. Attach variants to designs	Attaching is what makes a card visible. Until a design prefers a variant for a locale, no credential uses it.
4. Update or retire a variant	Maintenance comes last because a change or delete reaches every design that prefers the variant.

Kinds and locales

The console authors SIMPLE_CARD (colours plus a logo and optional background from the asset library) and SVG_TEMPLATE (a template asset uploaded first). Other kinds arrive through imports and open read-only. localeApplicability decides which locales a variant may serve, which is how one design carries a different card per language.

Deeper reference

Render Variants has the captured 11 Credential Designs requests 03 to 05.

Next journey

Continue with Define credential designs and claims.