Skip to content
All projects

Legal services · Employment law firm

Supra Laboris

Custom booking and payment system with service-based lawyer assignment, plus a full website redesign.

Status
PublishedWebsite, redesign and booking system published. Severance calculator redesign still in progress.
My role
Full stack developer — custom booking & payment system and full website redesign
Supra Laboris — screenshot of the website

Context

An employment law firm with offices in Toledo, Illescas and Madrid that sells online legal consultations. Clients choose a service, pick a time, pay and receive a video call link.

The technical problem

Each legal service has to reach the right lawyer, a time slot can never be sold twice, and the booking must end up in the lawyer's and the client's calendars with a Meet link and an invoice — without manual steps.

The solution

A custom WordPress plugin exposes REST endpoints for configuration, availability and booking. The booking page asks for the legal service first, filters the responsible lawyer, shows only their real availability and completes the payment with Stripe before creating the calendar event and the invoice.

Architecture & logic

  • REST endpoints for /config, /availability and /book consumed by a custom front end
  • Availability computed per lawyer from Google Calendar busy times
  • Each time slot is keyed by date and time, so the same hour cannot appear twice
  • The slot is re-checked at payment time to prevent double bookings
  • Service-to-lawyer mapping stored in the plugin settings as the single source of truth
  • Safe, incremental database migrations for new booking fields

What I built

  • Legal service selector that drives lawyer assignment
  • Consultation window and 45-minute slots enforced server-side
  • Accessible custom dropdown (keyboard, focus, outside-click) replacing the native select
  • New homepage and Toledo landing page in the redesigned visual language
  • Severance calculator redesign (in progress)

How it was verified

  • Endpoints checked on the live site (configuration and availability responding correctly)
  • PHP changes linted and diffed in isolation before release
  • Reported assignment issues traced to their root cause before changing any code