UNext | Online Appointment Booking Platform
A specialist discovery and online appointment booking platform built with Django and Tailwind CSS: a service catalog, specialist profiles and portfolios, a Jalali-calendar availability engine, deposit-based booking, and phone-based accounts.
UNext is a fully Persian, right-to-left platform for discovering specialists, browsing their portfolios, and booking appointments online, built from the ground up with Django and Tailwind CSS. The interface ships with the Estedad typeface, a dark mode, a mobile bottom navigation bar, and a responsive layout that feels equally native on phones and desktops — and the homepage opens the journey with real, live counts of services, specialists, articles, and users.
The service catalog keeps every row together with a description, a duration in minutes, an image, and an optional prepayment amount; images are cropped and resized to a standard 1200×900 the moment they are saved, then stored as WebP. Every specialist carries a public profile with a bio, an experience level, an average rating, and an Instagram handle, and the many-to-many service-specialist link lets the deposit for a service be set per specialist.
The availability engine has two layers: recurring weekly working hours (Saturday through Friday) for the everyday routine, and explicit Jalali date ranges whose days are materialized automatically and filled with 30-minute slots. Date ranges may never overlap, individual days can be deactivated for time off and holidays, and every change bumps a versioned availability cache so the times shown to customers always stay accurate.
Booking an appointment takes four steps: choose a service, choose a specialist, pick a month, day, and time on the Jalali calendar, and confirm. Available months, days, and times are served through AJAX APIs and computed from the service duration plus a 30-minute rest between appointments; times already past on the current day and windows that are already booked are excluded, and the chosen time is re-validated once more on the server at reservation. A uniqueness constraint on specialist, date, and time rules out double bookings.
Every appointment walks a complete status cycle — pending, confirmed, ongoing, completed, cancelled, and expired — and bookings whose time has passed expire automatically. A service without a deposit confirms the booking instantly; otherwise the customer continues to a review-and-pay page (the payment flow is gateway-ready and carries a built-in test mode). Appointment reminders go out as SMS from background Celery tasks, and a cancellation by the specialist notifies the customer by SMS as well.
Accounts come in two modes: username with a password, or a phone number with a six-digit SMS code (configurable). Iranian numbers are normalized to a standard format — Persian and Arabic digits and the +98 and 0098 prefixes included; the one-time code is stored hashed in the cache behind a validity window, an attempt cap, a resend cooldown, and separate rate limits per phone number and per IP. Registration runs through expiring tokens, changing the phone number makes verification mandatory again, and the My Appointments page lists bookings grouped by status and paginated.
Specialists get their own protected workspace: bookings managed in four lists — future, past, done, and cancelled — completing and cancelling appointments with an SMS to the customer, weekly working hours and Jalali date ranges with automatic day synchronization, deactivating specific days for time off, managing portfolio items, and moderating reviews with approve, reject, and delete actions.
Customer reviews carry a one-to-five rating, each customer may leave exactly one review per specialist, and reviews are published only after approval; the specialist's average rating is recomputed on every approval or deletion, and editing a review sends it back to pending. Portfolio items form the specialists' work gallery: each item can be tied to several services, the listing is filterable by service and paginated, and every item carries its own SEO metadata.
Site content is managed entirely from the database: interface texts are editable in the admin with keys, groups, and default values; the site name, tagline, light and dark logos, favicon, custom font, and the full color palette (validated as CSS colors) live in one branding record; and for every content type — service, article, specialist, and portfolio — a universal fallback image can be set, so a single file restyles the default image of an entire section. The articles section adds search, threaded comments, related articles, reading time, Jalali dates, and an in-admin SEO score.
The SEO layer gives every service, specialist, article, and portfolio item its own meta title, description, and keywords, and pages publish with Open Graph and Twitter tags plus JSON-LD structured data; the sitemap (static pages, articles, services, and specialists) and robots.txt complete the picture. The runtime serves over ASGI with Daphne, the production cache and channel layer sit on Redis, background SMS runs through Celery, the admin path is shielded from ordinary users by a dedicated middleware, uploaded images are validated, development and production settings are read from the environment, and subpath deployments — with dedicated cookies and reverse-proxy support — are supported.
- Technologies
- Python Django Tailwind CSS
Project team
Soheyl Mohammdi
Founder