Evaluate Cards, CRUD, Panel

Problem

• Multiple teams are working on similar concepts (Card, CRUD, Dashboard Panel) without clear differentiation
• Unclear when to use Card vs CRUD vs Panel components
• Need consensus on whether Panel should be a new concept or an extension of existing components

Goals

Make a clear recommendation for how we handle these component types moving forward—both as a group and individually. This includes defining:

• Whether Card and CRUD should remain separate components or be unified.
• Whether panel should be a standalone concept or a variant of Card or CRUD
• Identify additions or updates are needed to better support use cases across teams (e.g., guidance, variants, naming).

Todo

1. Evaluate Card, CRUD, and Panel concepts together to determine what should and shouldn’t be represented as standalone components.
   • Assess overlap between the Card component in Pajamas and the CRUD component.
   • Clarify scope of CRUD and Panel: define whether these are component-level concerns, broader layout/pattern guidance, or something else?
2. Recommend next steps for each concept individually, component update, deprecation, unification, documentation change, or no action.
3. Create issues as needed to follow up on implementation, guidance, etc...