Hospitality platform
Face B&B
2025 - PresentChallenge: Create a complete accommodation platform where hosts can publish, manage, promote, and monitor listings with a more human experience than classic OTA flows.
Delivery: Built search, filters, listing pages, host onboarding, subscription plans, media upload, calendar management, admin governance, multilingual support, wishlists, tracking, and GDPR-aware reporting.
Outcome: A scalable product ecosystem with clear growth loops, stronger listing control, and a conversion path ready for both hosts and travelers.

What it shows: Admin overview with KPI cards, tasks, requests, payment state and listing management areas.
Why I built it this way: I kept operational signals grouped on one screen so a host/admin can understand what needs attention before opening deeper flows.
Scope: Dashboard structure, status cards, pending actions, property controls and admin-side visibility.

What it shows: Long property-editing form with structured fields, amenities, pricing sections and media/listing configuration.
Why I built it this way: I separated data into predictable blocks because accommodation publishing has many required details and operators need confidence before going live.
Scope: Host onboarding, listing setup, form validation, amenities, pricing metadata and content management.

What it shows: Public listing page with gallery, host profile, booking panel, location map, services and reviews.
Why I built it this way: I designed it to answer trust questions in order: what the place looks like, who hosts it, where it is, what is included and what others say.
Scope: Listing detail page, booking intent, image gallery, host trust layer, map and review presentation.

What it shows: Search/filter experience with a vertical filter rail, detailed constraints and result area.
Why I built it this way: I made filters persistent because travel discovery depends on quick comparison without losing the current result context.
Scope: Advanced search, filter taxonomy, result refinement, location and accommodation metadata.

What it shows: Marketing/home flow with hero, property cards, hosting story, discovery sections and trust blocks.
Why I built it this way: I used an editorial structure to make the product feel warmer than a standard OTA while still keeping clear conversion points.
Scope: Landing page, featured listings, storytelling sections, host acquisition and credibility blocks.

What it shows: Alternative landing state focused on destination discovery, property cards and repeated conversion sections.
Why I built it this way: I repeated the core CTA pattern across the page to keep discovery and host acquisition visible even after scrolling.
Scope: Growth-oriented landing layout, listing previews, CTA rhythm, trust and discovery content.

What it shows: Host property-management screen with KPI cards, payment/action blocks and a property card.
Why I built it this way: I kept the active property visible in the same workspace as the operational counters so hosts can understand listing state quickly.
Scope: Host dashboard, property card, listing status, payment action, promotion flow and admin navigation.

What it shows: Light-theme Face B&B admin dashboard with KPI cards, pending actions, payment blocks and task sections.
Why I built it this way: I used a light administrative layout to make long operational pages calmer and easier to scan during daily host management.
Scope: Admin overview, task routing, property operations, payment signals and status monitoring.

What it shows: Light customer-facing booking/request form with long structured personal, stay and consent sections.
Why I built it this way: I used a clean light layout because external users need readability, trust and clear section separation when completing long forms.
Scope: Customer intake, booking request details, consent data, checkout information and public form completion.



















