We ship 10+ Strapi landing pages a month for clients, how do we not re-wire Croct every time?
Technical director at an agency. We run a landing page factory: shared Strapi setup, 10-14 client pages a month, same hero/form/proof-section structure nearly every time.
Adding Croct per project currently means a senior dev repeating the same slot wiring by hand. At our volume that is a day a month of senior time doing copy-paste work.
Can the setup be templated so a junior scaffolds it in minutes? And how do we keep clients separated, one account or one per client
2 answers
This is exactly what the CLI template commands are for. npx croct@latest init scaffolds the setup and generates slots.d.ts, and the CLI additionally supports use to apply a template and create template to produce one from an existing project. So the workflow for your factory:
- Wire your standard hero/form/proof structure once, properly.
- Run create template from that project.
- Juniors run use with your template on each new client project.
The Strapi-specific templating flow is written up in the Strapi integration templates post.
For client separation: workspaces. One organization, one workspace per client. The croct.json5 config file holds the organization, workspace, and applications per environment, so each scaffolded project points at the right client workspace from day one and nothing leaks between accounts.
We run an agency with a similar throughput. Two operational notes on top of the template answer:
- Commit the generated slots.d.ts per project. Type errors catch juniors wiring a slot to the wrong component shape before it ships.
- Standardize slot naming across clients (hero, lead-form, social-proof). When every project uses the same slot IDs, your template needs zero per-project editing and your team can context-switch between clients without relearning the setup.
Our scaffold time went from about half a day to under 20 minutes with this.