Carousel pattern (Publish to Site)

[dplsek]

Description

TBD.

Tasks

Checklist

Preview Give feedback

1. Density (HD, MD, LD, TD)
2. Mode (Light, Dark)

Deliverables

Preview Give feedback

1. Characteristics spec
2. Interactions spec, where necessary
3. In Code & Figma (Component + Guide)
4. Supporting site documentation

[shinytoyrobots]

Carousels are bad patterns - I don't think this is something that we should define or build, as doing so puts a design system approval on a fundamentally flawed UX.

[origami-z]

Bump to Q3, need more tech consideration before publish examples

[mark-tate]

Assume it depends on Deck layout #368

[bhoppers2008]

Needs discussion about whether carousel is a component or pattern. Related to #368

[mark-tate]

Tecno Goal: kickoff for this sprint

Decide whether a component or a pattern
Review Pepper

[mark-tate]

It's a component.

Aligning the old Carousel implementation with latest standards and removing DeckLayout from our Carousel.
DeckLayout will remain in Labs.

Call required with @ivan-calderon to align visuals.

[mark-tate]

Refactoring into a composable solution
Technical approach to be agreed by EOS, minimum design to be agreed by EOS

[mark-tate]

Oregano Goal
Publish pattern by EOS

[mark-tate]

catchup today to align the design with the implementation

[mark-tate]

refining the alignment of design and code

If you need this component, then let us know as we are looking for stakeholder reviews

[mark-tate]

On track

• Re-scoped, ticket to be updated. See re-scope details discussed

c.c. @joshwooding