Abstract and Centralize Tailwind CSS Configuration

[anuragxxd]

Description:

Currently, Tailwind CSS configuration may be duplicated or inconsistently managed across multiple packages in our monorepo. We have a scripts/tailwind/ directory but need better abstraction to share Tailwind config, theme tokens, and custom utilities across all packages without duplication. This will improve maintainability and ensure consistent styling.

Expected Behaviour:

• Shared Tailwind config package that all components can import
• Centralized theme tokens (colors, spacing, typography) matching ELIXIR Cloud branding
• Reusable custom utilities and plugins available to all packages
• Single source of truth for design tokens
• Easy to update styling across all components from one place

Approach:

1. Create shared configuration package (e.g., packages/ecc-tailwind-config/)
2. Extract common theme tokens, colors, and utilities used across packages
3. Export base Tailwind config that packages can extend
4. Update each package's tailwind.config.js to import and extend the shared config
5. Move design tokens to match with ecc-utils-design patterns
6. Update build scripts to handle shared Tailwind dependencies
7. Document how to use and extend the shared configuration