Client work · Automotive

CarNova AutoSales

A car dealership website that the dealer runs himself. Stock changes weekly, so the site had to be an application, not a brochure.

Visit carnovasales.eu
The CarNova AutoSales website, showing the vehicle listings
Black and red identity, vehicle galleries built for thumbs, listings served from Firestore.

The client

A car dealer whose inventory turns over constantly. Cars sell, new stock arrives, prices move — and none of that can require a phone call to a developer.

What they asked for

A website with the dealership's character — bold, black and red, unmistakably automotive — where customers can browse the current stock properly, and where the dealer can add or remove a vehicle himself.

The constraints that mattered

  • The content changes weekly. Anything hard-coded would be wrong within a month.
  • The customer is on a phone, usually looking at photos, usually with one hand.
  • Two languages, Greek and English, for a market where both matter.
  • Non-technical owner. The admin panel has to be usable without training or documentation.

What I delivered

  • Firestore-backed vehicle listings, so the site reflects real stock rather than a snapshot from launch day.
  • A secure admin panel for adding, editing and removing vehicles.
  • URL-driven listing pages — every vehicle has its own address that can be sent to a customer.
  • Touch-optimised galleries, built around swiping rather than clicking.
  • Bilingual EL/EN across the site.
  • SEO and Open Graph metadata, so a shared listing shows the car rather than a generic logo.
  • Performance tuning, because a gallery-heavy site on mobile data is slow by default.
The CarNova listings page, with category, availability, gearbox and fuel filters above the vehicles in stock
Current stock, straight from Firestore: filters for category, availability, gearbox and fuel, and each vehicle on its own URL.
The CarNova customer reviews page in the black and red identity
Customer reviews, in the same black-and-red identity that runs through the rest of the site.

Two decisions worth explaining

Every listing gets a real URL

A dealer's actual sales motion is sending a specific car to a specific person. If the listing only exists inside a filter on the homepage, there is nothing to send. Giving each vehicle its own address made the site work the way the business already worked, and gave search engines something to index.

Cost: listing pages have to handle vehicles that have been sold and removed, rather than simply disappearing.

An admin panel instead of a CMS

A general-purpose CMS would have given the owner fifty options he does not need and one he does. A purpose-built panel does exactly the four things a dealership does — add a car, edit it, photograph it, remove it — which is why it gets used.

Cost: anything outside those four things needs me. That is a deliberate trade, not an oversight.

The result

Live at carnovasales.eu, with the dealership managing its own inventory.

It is the most application-like of the client sites I have built: the visible half is a website, and the half that determines whether it stays useful is the data layer and the admin panel behind it.

Have a project in mind?

I take on client websites, web apps, and product builds across Cyprus and Greece.

Start a conversation