Github

Icon Set Collection

Create collections of icons for use in your front end.

Atomic Payload Is Not Recommended For Production Builds At The Moment

Overview

While you can upload and optimize icons in the Icons Collection, we need a middle layer between them and the Icon Child Block. We need this middle layer because without it, we could change individual Icons and those changes would persist. But if we want to test an entirely different Icon collection/set, we need an Icon Set collection.

Here is a brief overview of what Icon Sets includes:

  • Active checkbox toggle to determine which Icon Set is currently used by the website
  • Test path for viewing changes in the same screen with live preview
  • Array of Icons, where you can set the name for use by the Icon Child Block, and a relationship field to an asset in the Icon Collection.

Notes

It is recommended you maintain a consistent naming structure across your Icon Sets. Since the front end uses the name string values to find the correct asset.
Active status utilizes draft mode. Meaning you can demo different sets and their impact on your site in draft mode, without exposing it publicly.
Publishing an update to the Icon Set will automatically apply to all live pages, unless the Icon Set is not active.