Migrating to Blossom Carousel

Blossom keeps the carousel as a native scroll container. Most configuration from other libraries becomes CSS, navigation becomes Blossom's control components or methods, and many plugins become browser features. Migrations usually delete more code than they add.

Workflow

1. Identify the source library and the project's framework from package.json and imports. If several libraries are in use, migrate one carousel at a time.

2. Fetch the matching guide:

   • Embla: https://www.blossom-carousel.com/raw/docs/migration-guides/embla.md
   • Swiper: https://www.blossom-carousel.com/raw/docs/migration-guides/swiper.md
   • Splide: https://www.blossom-carousel.com/raw/docs/migration-guides/splide.md
   • Slick or react-slick: https://www.blossom-carousel.com/raw/docs/migration-guides/slick.md
   • Flickity: https://www.blossom-carousel.com/raw/docs/migration-guides/flickity.md

   For any other library (Glide, Keen Slider, Owl, Tiny Slider, and so on), say there's no dedicated guide and use the mapping below.

3. Load the framework skill for implementation details: blossom-carousel-vue, blossom-carousel-react, blossom-carousel-svelte, or blossom-carousel-web.

4. Inventory what the existing carousel actually uses (options, methods, events, plugins, CSS overrides). Map each item, and tell the user which features have no direct equivalent before you remove them.

5. Replace the markup, move configuration into CSS, swap the controls, and then remove the old package, its CSS imports, and any dead wrapper styles.