Contact person: Figma-to-Tailwind Design Migration

Phone:Show

Email:Show

Location: Krakow, Poland

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I’ve finished the full UI for [login to view URL] in Figma and now need the visuals rebuilt with Tailwind CSS. The site targets senior travellers, so everything has to work flawlessly on desktop and mobile screens. While coding, please keep the exact layout structure and our colour-branding choices intact; typography can follow Tailwind defaults as long as spacing and hierarchy match the comps.

Accessibility is non-negotiable: every component must read well with screen readers, support high-contrast mode, and be fully operable from the keyboard. If you have a favourite plugin or ARIA pattern that speeds this up, feel free to use it—just keep the markup clean and semantic.

What I expect back:
• Pixel-faithful Tailwind HTML for all Figma pages and states
• Re-usable component classes (no inline styles)
• Documentation notes on where you’ve handled screen-reader labels, contrast variables, and keyboard focus rings
• Template should use Twig Template engine (as application will be in PHP Symfony)
• Only pure JS ,no frameworks. JQuery is allowed.
• All texts should be packed into strings that can be translated using TWIG translations.
• All things that should be content passed from backend when template is render should use TWIG way of doing this (double bracket {{ }} )
• Template should be made from simple subtemplates (using extends , import from TWIG) .

For easy work and be sure that template will work you should create skeleton of Symfony Web App with use of Webpack Encore. We expect link to git repository to show work done, repository should be private.

I’ll share the Figma link and design tokens as soon as we start so you can jump straight into coding.

If we will be happy of result of work, we would like to order other pages." (client-provided description)