The Power of Strapi Custom Fields for Plugins Creators
summary
Custom fields embed third‑party integrations directly into the content editor so editors never leave the page, implemented as plugins via the plugins SDK. They arrive in Strapi v4 and gain developer conveniences in v5, can be published to the Marketplace, and support settings pages. Examples: an emoji field built in a few lines of code, product sync that surfaces commerce data in the content API, and navigation/comments plugins that reuse fields across projects and work in production.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 1:28What are custom fields?
- 2:44Benefits and evolution
- 3:30How to create and use fields
- 5:18Advanced plugin usage
- 6:38Integration and workflows
- 7:39Conclusion and Q&A
related talks
03h 16mIntegrate Stage
16mKeynote
30mWise approach for community & commercial Strapi plugins development
08mDeep dive into the plans for Strapi v4
07mBoosting Productivity and Team Velocity with Strapi
03h 18mBuild Stage
31mEditorial workflows, GIT them here!
29mBuilding custom Figma plugins to unlock new capabilities