Replace SLDTridionWorld Link to SDL Appstore
Source Link
Chris Mills
  • 2.2k
  • 1
  • 11
  • 18

Check out Serguei Martchenko's Template Building Block Type Indicator eXtensionTemplate Building Block Type Indicator eXtension as an example to extend icons.

His config includes a match for TBBs which maps to specifically named icons in a separate "themes" folder:

<ext:itemicons>
  <icon match="^T2048L[01]P0S[1-7]$" path="${theme}Images/${icon}.${size}x${size}.png" />
</ext:itemicons>

Depending on your use case, it's probably better to add custom scenarios as an extension, which will make managing this easier across CMS environments and especially for upgrades.

Check out Serguei Martchenko's Template Building Block Type Indicator eXtension as an example to extend icons.

His config includes a match for TBBs which maps to specifically named icons in a separate "themes" folder:

<ext:itemicons>
  <icon match="^T2048L[01]P0S[1-7]$" path="${theme}Images/${icon}.${size}x${size}.png" />
</ext:itemicons>

Depending on your use case, it's probably better to add custom scenarios as an extension, which will make managing this easier across CMS environments and especially for upgrades.

Check out Serguei Martchenko's Template Building Block Type Indicator eXtension as an example to extend icons.

His config includes a match for TBBs which maps to specifically named icons in a separate "themes" folder:

<ext:itemicons>
  <icon match="^T2048L[01]P0S[1-7]$" path="${theme}Images/${icon}.${size}x${size}.png" />
</ext:itemicons>

Depending on your use case, it's probably better to add custom scenarios as an extension, which will make managing this easier across CMS environments and especially for upgrades.

Source Link
Alvin Reyes
  • 12.6k
  • 4
  • 20
  • 61

Check out Serguei Martchenko's Template Building Block Type Indicator eXtension as an example to extend icons.

His config includes a match for TBBs which maps to specifically named icons in a separate "themes" folder:

<ext:itemicons>
  <icon match="^T2048L[01]P0S[1-7]$" path="${theme}Images/${icon}.${size}x${size}.png" />
</ext:itemicons>

Depending on your use case, it's probably better to add custom scenarios as an extension, which will make managing this easier across CMS environments and especially for upgrades.