Home / Companies / Strapi / Blog / Post Details
Content Deep Dive

Finding and using Strapi design system icons in your plugin

Blog post from Strapi

Post Details
Company
Date Published
Author
Theodore Kelechukwu Onyejiaku
Word Count
1,541
Company Posts That Month
28
Language
English
Hacker News Points
-
Post removed?
No
Summary

Strapi plugin developers can select icons from the maintained Strapi Design System icon catalog, community viewers, or a locally generated gallery that enumerates the exact exports installed in their project. Icons are imported from the separate @strapi/icons package and used differently depending on context: plugin navigation links and custom-field registrations require a component reference, while buttons and other JSX components require rendered icon elements. SVG icons can be resized and styled with theme-aware design-system color tokens, whereas branded and field-type symbols from @strapi/icons/symbols have built-in colors and should generally only receive dimensions. The guidance also notes major naming and package-location changes in Design System v2, recommends consulting migration resources when porting older plugins, and advises declaring the icon and design-system packages as peer dependencies to avoid duplicate React trees. Developers are encouraged to check imports first when an icon silently fails, use consistent domain-relevant iconography across plugin interfaces, and avoid duplicating icons already associated with Strapi’s core navigation.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.