Assets

While assets are not part of a style family, they can be made to be retrieved by the style family resource lookup algorithm. This works by putting them in a folder structure similar to the style family inside of Assets. See Resource lookup algorithms for more information. The supported assets for lookup are Custom.js, Custom.css and images.

The same Assets folder structure must be used in the style family folder as in its default location. For example, if an image file plus.png resides in the Images folder, and you want to use another version of it when the style family Infor/Lightness is used, the new plus.png image file should be put in the Infor/Lightness/Images folder.

The folder in which a style family folder is placed can be either the root of Assets, a locale folder, or another style family folder (representing a style family that is part of a style family hierarchy). If an asset is both localized and using a style family, the locale folder must be the one in the root.

Again, assets are not part of a style family, so if you delete a style family, it will remove only user-defined styles, not assets. You must delete assets separately. Also, if you copy a style family, the copy will not include versions of asset files. If you copy an asset, you will get a copy of that one single file. If you want to copy a styled or localized asset, you must navigate to it and copy it separately. If you export a style family, assets are not exported. You must export them separately. Every asset is managed separately, including each styled and localized version. Each must be exported separately.