Empty States guidance

[laurenmrice]

Acceptance criteria

Core

• The Core empty state pattern is lacking product specific guidance and is outdated.

Product

• Product has a more thorough point of view on the content and illustration in their empty states component that Core needs to inherit. Is there any additional material that needs to be created to support this information to make it more robust to live on the Core site?
• Product has a ‘stable’ coded pattern and an experimental empty state v2 pattern

Workgroup

• There is also a work group happening on the already established empty state guidance. We need to bring all of this together as a cohesive point of view in Carbon core.

Tasks

Preview Give feedback

1. [Empty States] Synthesize + Meet the work group #17554
   role: design ✏️ +1
   
2. [Empty States] Consolidation meeting with workgroup #17980
   role: design ✏️ +1
   
3. [Empty States] identify design aspects that still need to be resolved carbon-website#4384
   role: design ✏️ type: docs 📖 type: enhancement 💡 +3
4. [Empty States] Variants and use cases #18524
   role: design ✏️ +1
5. [Empty States] Formatting #18525
   role: design ✏️ +1
6. [Empty States] Behaviors #18526
   role: design ✏️ +1
7. [Empty States] Types and alternatives #18527
   role: design ✏️ +1
8. [Empty States] Defining the empty state as a component or pattern #17557
   role: design ✏️ +1
9. Have a meeting with dev to get their take on how we should be moving this code
10. [Empty States] Consolidate documentation
11. [Empty States] Finalize documentation
12. [Docs]: Empty-state message topic: image, content (text), and screen capture suggested improvements carbon-website#4314
    role: design ✏️ severity: 3 type: bug 🐛 type: docs 📖 +4

For future refinement Keeping column headers in empty states

REF carbon-design-system/carbon-website#4314