Skip to main content
This is where Florence pulls away from single-chart tools. A brand kit is a regular project you mark as a brand kit. Its styles, templates, and themes become available to any project that links it — the same idea as publishing a Figma library.

​
Styles

In Assets → color styles and text styles:
  1. Create a style (font, size, line height, color, and the rest for text; a color token for fills).
  2. Apply it from the Properties panel (text style picker, color style connector).
  3. Edit the style in Assets. Linked text and colors update across the project.
Chart value labels and line labels can use the same text styles.

​
Templates

  1. Build a frame you expect to reuse (headline / chart / footer is the usual one).
  2. Select the frame → Assets → Templates → Save as template.
  3. In any project that can see that template, click it to insert a new frame.
Change the copy, swap the dataset, override colors. V1 is a smart copy of the source, not a live component instance. Treat “Update” / “Reset” on an inserted template as source-sync tools when they appear — do not assume Figma-style component bindings yet.

​
Themes

Save a theme from a frame when the look is right but you do not want to copy the words or the data. Applying a theme restyles a frame (and its children) without rewriting content, size, or layout direction. Named starters — Editorial, Minimal, Bold — are frame themes. Use them as a first paint, then save your own.
  1. In the brand-kit project: file menu → Mark as brand kit.
  2. Publish the brand kit when you want others to consume it (brand kit publish is the wired publish path).
  3. In a working project: Assets → link the brand kit. Styles, templates, and themes from the kit show up as linked assets.
Linked styles follow the kit. A dedicated Update control for “the kit changed after you linked” is not shown yet — linked styles are read-only in the consuming project and refresh when the kit changes.

​
How this looks in practice

A studio producing a long-running client package (the Yelp graphics we make at DataFace, for example) would:
  1. Create a Yelp brand kit project.
  2. Save Yelp red / teal as color styles, and the type hierarchy as text styles.
  3. Build the frames that get reused (header + chart + footer, small multiples, image beside chart) and save each as a template.
  4. Save “Yelp simplified” and “Yelp dense” as themes.
  5. On the next deliverable, link the kit, insert the templates, connect new datasets, and apply the theme that matches the story.
One kit, many projects, same graphic language.