Paid UX UI Design Trial - Additional work available for suitable candidate

-- Introduction This paid trial is intended to simulate a realistic design engagement rather than a traditional design test. The objective is to understand how you approach problems, communicate decisions, build scalable systems and collaborate with others. There is intentionally no single “correct” solution. We are interested in your judgement as much as your final output. Please document any assumptions you make where information is incomplete or ambiguous. -- Time Allocation Submission is due within 24 hours of you receiving the Figma link to the core Brand styles which will include: -Fonts (Google) -Core colours -Logo With this, you will also receive: - some website addresses to use as UX / UI references - some hypothetical Company details The objective is not to create a perfect solution, but to demonstrate how you prioritise your time and make design decisions under realistic constraints. Quality of thinking is valued more highly than quantity of output. -- Project Design the first iteration of a scalable design system and apply it to a modern Resource Centre experience. Assume this product is built using React and ShadCN components. The Resource Centre is powered by a CMS and all content is dynamic. Your design should accommodate a wide variety of real-world content without requiring redesign for individual cases. -- Objectives Create a solution that demonstrates: -Clear visual hierarchy -Scalable component thinking -Excellent usability -Thoughtful interaction design -Developer-ready documentation -Strong communication of design decisions -- Deliverables 1. Design System Foundation Create an initial design system suitable for long-term product growth. This should include the foundations required to support the Resource Centre and future product expansion. Examples may include: -Typography -Colour system -Spacing -Layout/grid -Elevation -Iconography -Components -Tokens -Variables -Variants Use Figma Variables, Styles and Components where appropriate. 2. Resource Centre Design a responsive Resource Centre that allows users to discover and browse content. Include appropriate consideration for: -Search -Filtering -Sorting (if applicable) -Featured content -Resource cards -Categories -Tags -Metadata -Responsive behaviour The page should comfortably support different quantities and types of content. 3. Resource Detail Design a representative Resource Detail page using the same design system. Consider: -Content hierarchy -Rich content -Related resources -Calls to action -Navigation back to browsing 4. Subscription Experience Design a subscription experience that encourages users to receive future content updates. The implementation is intentionally open-ended. Consider: -Entry points -Context -User journey -Appropriate interaction pattern -Success and failure states -Friction vs engagement Document any assumptions you make. 5. Global Navigation Design a reusable global header and footer appropriate for the product. They should demonstrate scalable navigation rather than simply supporting this single page. 6. Prototype Prototype key interactions that help communicate the intended experience. This does not need to be exhaustive. 7. Developer Handover Prepare your Figma file so another designer and a front-end developer could confidently continue the project. Include any documentation you feel is appropriate. -- Design Considerations The following scenarios should be considered if / where appropriate: -Empty states -Loading states -Skeleton loading -Success states -Error states -Missing images -Variable title lengths -Variable description lengths -Multiple tags -Single tag -No tags -Featured content -External resources -Different content types -Responsive layouts You do not need to produce separate screens for every scenario. -- Constraints Use the core styles provided as a foundation to expand on Build using a scalable design approach. Assume React + ShadCN implementation. Components should be reusable wherever practical. Designs should be responsive. Accessibility should be considered. Content is managed through a CMS. -- Submission Please provide: -Figma file -Prototype -Any supporting documentation -- Reflection If you wish to do so, you may include a written summary to accompany your submission that communicates the thinking behind the work, eg.: -Your overall approach -Key assumptions -Design trade-offs -Areas you intentionally chose not to explore -If you had one additional working day, what would you improve first and why? -- AI AI-assisted workflows are welcome. Please briefly outline: -Which tools you used -How they were used -Which decisions remained your own