Voliop

Problem

Equestrian buyers and sellers needed one place to trade horses, join auctions, rent stables, and book vets and trainers, without juggling fragmented sites or unclear trust signals.

What I built

Frontend for Voliop (voliop.vercel.app) under Why Not Tech (freelance / project-based): a fast, responsive Next.js and Tailwind UI spanning marketing pages, listings, categories, and core marketplace journeys.

Key features

• •Responsive interface across breakpoints with performance-minded page structure
• •Category and listing experiences with dynamic routing across marketplace verticals
• •Login and registration flows wired into the product’s auth model
• •Bilingual support (English and Arabic) with correct RTL/LTR behavior
• •Integrations with backend and external APIs for live data and services

Tech stack

Challenges & solutions

• Challenge

  Serving two reading directions and languages without duplicating layouts or breaking component reuse.

  Solution

  Direction-aware layout primitives, shared components tested in both LTR and RTL, and consistent spacing and typography rules per locale.

• Challenge

  Many marketplace modules (auctions, rentals, services) on one brand without a noisy UI.

  Solution

  Repeated section patterns, clear hierarchy per page type, and predictable navigation between categories and detail views.