Translate the website to Tailwind CSS and NextJS, Shadcn UI

Transfer the existing site from NuxtJS to NextJS (App Router) and completely switch from custom CSS to Tailwind CSS, using Shadcn UI for basic components. Visually, the site should remain as similar as possible to the current design (minimal deviations are allowed if necessary for standardization through Tailwind).

Scope of Work

1) Framework Migration

• Transfer pages/routes from Nuxt to NextJS (App Router).

• Preserve the existing structure of pages, navigation, URLs (or add 301 redirects if they change).

• Connect Shadcn UI and set up the basic design setup.

2) Full Transition to Tailwind CSS

• Remove/minimize custom CSS (keep only if:

  • they are variables/tokens,

  • or small global resets/utilities that cannot be adequately done with Tailwind).

• All layout, spacing, typography, colors, borders, shadows — through Tailwind utility classes.

• All UI components (buttons, inputs, cards, modals, nav, footer) — either through Shadcn UI or custom components on Tailwind (but without “old” CSS).

3) Shadcn UI Integration

• Use Shadcn components as a base (Button, Input, Dialog, Dropdown, Tabs, Toast, etc.).

• Unify styles so that components look consistent with the site.

Requirement for Visual Consistency

• The design must remain plus-minus the same as in the current version:

  • typography (sizes, weight, line-height),

  • spacing (padding/margin),

  • colors,

  • rounded corners,

  • shadows,

  • container widths and breakpoints.

• Small deviations are allowed, but the overall “visual language” must match.

Definition of Done

• The NextJS project runs, builds, and deploys without errors.

• There is no dependency on old custom CSS (or it is minimized with a clear explanation of why).

• All pages display correctly and match the design.

• Tailwind Plus UI Blocks are inserted and look as close as possible to the demo (fonts, spacing, colors, container).

• Shadcn UI components are stylistically consistent with the site.