Top 10 Strapi Tips
summary
Ten concrete Strapi v3 tactics: file layout (api, components, config), request flow through middleware to controllers/services/queries, and the blueprint override pattern to replace find/findOne/create/update/delete with custom logic. Use beforeCreate lifecycle to auto-generate slugs and afterFetch to pull Shopify data by storing a shopify id and merging remote fields. Implement per-user filters by forcing author-id in the find controller, expose custom routes for fixed filters, and split admin and API to deploy the React admin separately. Plugins add audit, comments, menus.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:54Strapi project architecture & key concepts
- 2:05How an API request is managed in Strapi
- 3:06The customization of a Content-Type controller and service
- 3:47The edition of the content manager view
- 4:25Usage of life cycle functions for automations
- 5:06Manage its own data, from a end-user perspective
- 5:51Connect a third party like Shopify
- 7:16Split admin and backend deployment
- 8:16Plugins
related talks
28mBest Practices with Strapi, Next.js, and v0
18mSeamless UX with Advanced Technology in the Digital Era
27mSails Ahead: Powering App and Web Success with Strapi
08mShift gears, not code: How a French E-Bike Brand Hacked Digital Flow
33mRebuilding the Future: How We Transformed Our CMS with Strapi
10mAI Powered Strapi Optimizing Content Workflows
07mAccelerating Composable Commerce with Strapi
11mHow we used Strapi to simplify our LMS