react-components

To build production-grade React components with Next.js 15 and TypeScript strict mode, design mobile-first layouts styled with Tailwind CSS and shadcn/ui, ensuring WCAG 2.1 AA accessibility and FR/EN i18n via next-intl.

Yes, this React component approach supports offline-first PWA patterns by integrating next-pwa and Workbox, ensuring components remain functional and ready under offline network scenarios.

Manage state and forms by using Zustand for client state, TanStack Query v5 for server state, and React Hook Form combined with Zod for schema validation, ensuring robust data handling within your components.

The best way to ensure WCAG 2.1 AA accessibility in shadcn/ui components is to design them with mobile-first responsive layouts down to 320px, strictly adhering to accessibility requirements throughout the Sira platform implementation.

Yes, you can handle bilingual FR/EN translations by wiring next-intl into your components, ensuring the interface properly displays translations for both French and English locales.

You should not use Tailwind CSS with shadcn/ui if your project does not support Next.js 15 App Router or requires state management and validation libraries outside the specified Zustand, TanStack Query, and Zod ecosystem.