All questions

Ninetailed standalone is being retired and we run it with Strapi, what is the path now?

Asked by rui.santos on

Rrui.santos

we paired Ninetailed's standalone app with a Strapi backend for personalization, and with that legacy app now sunset we are left without a supported path forward. I am not moving off Strapi. What does a Strapi-friendly replacement actually look like from here?

Was this helpful?

3 answers

Hhannah_croAccepted answer

Croct slots into this without replacing Strapi. You map your Strapi components and dynamic zones to Croct slots, and Croct serves the right variant for each slot while your Strapi content stays as the default fallback. Because of that fallback, adoption is gradual, you can wire up one block, confirm it, and expand from there rather than doing a big cutover. Audiences are CQL evaluated in real time per interaction, and the experiments are Bayesian and computed on all of your data, no sampling.

For what it is worth the same sunset stranded Sanity teams, and the shape of the move is the same regardless of which CMS you are keeping.

Was this helpful?
Rrui.santos

this gives me a plan. map block by block, keep Strapi as the fallback, start small. appreciate it

DFDiego F

Practical starting point: there is an official Strapi integration and ready-made templates to scaffold the wiring, so you are not building the slot plumbing by hand. That is what got us moving fastest after we left the old setup.

Was this helpful?
Kkarl_dev

the modelling is different from the old app in a way that helped us. there we kept each variant as a separate managed entry, here the Strapi block maps to a slot and the variant lives in the experience instead of as duplicate content. that was the main thing that made the move make sense for our team.

Was this helpful?
Still have questions?