Replies: 1 comment
|
Hello @usman7g, Let me help you - but first clarify.
Now to help you with the questions.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
We note that the core @aegov/design-system package has been released at version 3.0 and is built on Tailwind CSS 4, while the installation documentation for @aegov/design-system-react specifies Tailwind CSS 3.4, and the React repository does not currently show any published releases.
Our questions are as follows:
Is the React package planned to be updated to align with Design System 3.0 and Tailwind CSS 4, and if so, is there an indicative timeline?
Is a React-based implementation fully supported for the purposes of the Design System compliance assessment?
Where the React package is not yet at parity with version 3.0, would it be acceptable to implement components in React using the core @aegov/design-system package directly, provided visual and behavioural parity with the published components and WCAG 2.2 conformance are maintained?
Is there any recommended guidance for teams building React or Next.js projects on the Design System?
Your confirmation will help us define the correct technical approach and ensure the delivered website meets the Design System criteria in full.
Thank you for your time, and for the continued work on the Design System.
All reactions