Allow your sites to load your design systems
List the sites your products run on, so your published design systems' fonts and files load there.
Your published design systems load in your products from the portal. Some of their files, such as licensed fonts, load only on sites you allow, so they stay on your own products. You need this before products can show your design system's fonts.
What it covers
- Only on allowed sites: fonts, the design system's manifest and its icon sprite, which browsers fetch from another site.
- Anywhere: the stylesheet and logos.
The portal itself is always allowed.
Add your sites
- Go to Organisation settings › Allowed sites (
/admin?tab=sites). - In Origins, enter one site per line, with the scheme and host only:
https://app.acme.com. Add a port only if the site uses one:http://localhost:3000. - Choose Save.
Leave out paths and trailing slashes: https://app.acme.com/dashboard isn't an origin. You can list up to 50 sites.
Remember the sites you test on as well as production, such as a staging address or a local development server.
Check it works
Open a page of your product that loads your design system's stylesheet. Its text should use your design system's fonts. If it falls back to another typeface, open the browser's developer tools: a blocked font request names the origin to add.
If something goes wrong
| What you see | What to do |
|---|---|
| "… isn't an origin" | Remove the path and anything after the host. |
| Fonts don't load on one site | Check the exact scheme, host and port: https://acme.com and https://www.acme.com are different sites. |
| Fonts don't load anywhere | Check the design system is published and the product uses its current address (Use your design system). |