Carousel

Use a carousel when several related messages or images deserve the same prominent spot but should not all appear at once. Content authors maintain which pages or slides appear; visual designers set timing, height, and motion so the experience stays calm and readable. Always provide a way to pause or move slides manually.

• Slides advance with controls and optional auto-play timing.
• Edit mode exposes drop targets for authoring slide pages.

1. Carousel root with a unique id.
2. Slide region with one panel visible at a time.
3. Previous and next controls (and optional indicators).

Replace with controls, indicators, and pause behaviour.

Authors maintain the pages multifield (or equivalent), height, randomization, and advanced classes through the component dialog.

Do

• Provide non-motion alternatives or ensure pause is discoverable where policy requires.
• Limit slide count to keep load and authoring manageable.

Don't

• Don't set very fast intervals; it harms reading and vestibular comfort.

• Hero-style rotating banners tied to existing pages or shared slide content.
• When auto-rotation is acceptable and can be paused by the user.

• Arbitrary component slides in one carousel; use Carousel (multi-item) (carousel-parsys) instead.
• Critical content that must not move; static Hero or Grid container is safer.