Fonts, Icons, and SVG

Pixflow Design should use Bricks-native systems for fonts and icons where possible.

Google fonts

When a design uses Google fonts, Pixflow should install them into Bricks first, then reference them through Bricks typography options and theme styles.

If the original font is not available from Google Fonts, Pixflow should choose the closest visual match and explain that substitution.

The Google Font Installer is available from the Pixflow settings modal. Use it when a generated design, HTML to Bricks handoff, or manual site setup needs a font that is not already installed in Bricks.

Icon sets

Custom icon sets should be installed through Pixflow’s icon builder/installer. After install, the builder should refresh its icon registry so newly installed icons can be selected without a full page reload where possible.

The Icon Builder is available from the Pixflow settings modal. Use it to install, sanitize, and manage custom SVG icon sets for Bricks.

Icon sizing

When HTML is converted to Bricks, icons should keep the size from the original design. Do not default every icon to 24 by 24 unless the original design uses that size.

For custom SVG icon libraries, width and height belong in the Bricks icon configuration and should be supported by classes or theme values where appropriate.

SVG elements

SVGs are allowed when SVG support is enabled in Bricks settings. Pixflow should not replace SVGs with placeholders just because they are SVGs.

Use Bricks SVG elements or supported icon controls when they match the source design.