← All projects
Freelance · Pharmacy marketplace

Ouipharma

Gradual redesign of the frontend of a pharmacy marketplace: pharmacies for sale, job offers and content for pharmacists.

Role
Freelance frontend developer
Period
2021 – 2023
Team
With another developer, then alone on the frontend
Environment
Ruby on Rails
Stack
Tailwind.css, Stimulus.js, Sass, HTML
Ouipharma: the redesigned home page, and a listing page on mobile
The home page on desktop and a listing on mobile
Context

Buy, sell, partner, recruit

Ouipharma is a listings platform for pharmacists: users can sell or buy a pharmacy, find a business partner, and post or browse job offers.

I joined Ouipharma in March 2021, on a site that had been online for several years. At first, I worked with another developer. Then I handled the frontend on my own, with help on the back-end when needed.

My role: redesign the interfaces page by page, adapt them to mobile, and integrate the interfaces of the user area. I also made design proposals, and worked with the CEO on SEO.

At the same time, we replaced the old CSS libraries (Semantic UI, then Bootstrap) with Tailwind.css.

What I did

A refresh of an existing site

Listings

  • 2021Listing pages: redesign of the pages by region, department and city.
  • 2021
    2023
    Listing detail page: new versions and mobile adaptation in 2021, then a layout redesign in 2023.
  • 2021Post a listing: new presentation page.

Home and navigation

  • 2022Home page: redesign of the mobile version, work on mobile performance and a new search bar.
  • 2023Menu: navigation adapted to tablet and mobile.

Content

  • 2021Blog: redesign of the article list and the article page, with an article carousel and share buttons.
  • 2021Pricing: redesign of the subscription plans page.
  • 2023Content pages: redesign of more than twenty pages (buying and selling guides, pharmacist salary, legal pages), with reusable components.

User area

  • 2021
    2022
    My listings and back-office: mobile adaptation of the management pages.
  • 2022Messaging: design proposal and integration of the new page, on desktop and mobile.

CSS code

  • 2022CSS cleanup: removal of Semantic UI, then of Bootstrap with the team, in favor of Tailwind.css.
Before / after

The pages I redesigned

Click a screenshot to enlarge it.

Listing page

My first redesign on the project: the long column of links to cities moves to the bottom of the page, and the listings take up all the space. Here, the Loire-Atlantique department.

Before · 2021
After · 2022

Listing detail page

New layout: key information at the top, the sign-up form on the right, and a reworked mobile version.

Before · 2021
After · 2023
Before · 2021
After · 2023

Blog

Articles are now shown in a grid, with the author, date and reading time. On the article page: a more airy layout, share buttons and an “All other articles” carousel, built with Glide.js.

Before · 2021
After · 2022
Before · 2021
After · 2022

Pricing

New subscription plans page, organized by need: selling a pharmacy, finding staff, partnering or investing.

Before · 2021
After · 2022

Home page

The home page changed in two steps: the previous team added the search tabs in 2020, then I redesigned the search filter, the listing cards, the buttons and the mobile version in 2022.

Before · 2019
After · 2022
Interface redesign

Design and integration

Example: the messaging page, from design proposal to integration, on desktop and mobile.

Messaging on desktop: list of conversations on the left, message thread in the center, contact details on the right
Messaging on mobile: search and list of conversations
Desktop version · June 2022  ·  Mobile version · July 2022
What I learned

Redesigning a site, page by page

At first, I made light changes, so that the redesigned pages stayed consistent with the ones that had not been redesigned yet.

In the end, over two years, almost all the pages were redesigned. They stayed consistent, but without a shared reference, it was hard to check: not forgetting anything, and avoiding small differences from one page to another.

Looking back, I would start from mockups or a design system for the whole site. That would have made these checks simpler, and allowed me to make bolder visual choices.

Screenshots taken on local copies of the site, with fictional listings and contacts. The years show the state of the site at that time: some visible elements were added by other team members.