Skip to content
Mehdi Messaoudene
Website & technical catalogue · client2025 - todayin production

BioInteraction DZ

The reference catalogue for in vitro diagnostics in Algeria - 418 reagents, 19 analysers, two languages.

Where it started

A distributor of laboratory reagents and equipment whose whole catalogue lived in PDFs sent by email. Biologists could not find references, the sales team sent the same technical sheets ten times a week, and Google did not know the company.

What was built

A complete, indexable technical catalogue with product sheets, downloadable leaflets, editorial hubs by brand, a blog and a customer area. Served as static HTML from shared hosting - so fast and hard to break - with Supabase for everything that moves.

Results

418
reagent references
19
analysers
273
translated sheets
2
languages

Interactive demo

A catalogue you can really query

Search a reference or an analyte. The filter is exactly the one on the production site.

24 results out of 24

  • XSYS0001ALB 440AlbuminERBA · 2000 tests
  • XSYS0002ALP 110Alkaline PhosphataseERBA · 500 tests
  • XSYS0003AMY 110Alpha AmylaseERBA · 500 tests
  • REG00065EC cartridge XSERBA · 250 Tests/2 mois
  • REG00058EC cartridge SERBA · 500 Tests/3 mois
  • REG00056EC cartridge MERBA · 1000 Tests/3 mois
  • HEM00028Erba H360 DilERBA · 20 L
  • HEM00029Erba H360 LyseERBA · 500 mL
  • HEM00023ELite H CleanERBA · 50 mL
  • EHL00001ERBA Protime TPERBA · 4x5 mL
  • EHL00003ERBA Actime TCKERBA · 6x5 mL
  • EHL00005ERBA Thrombin Reagent FIBRINOGENEERBA · 2x5 mL
  • URPH0028DekaPHAN LauraLeucocytes, Nitrite, pH, Protéine, Glucose, Urobilinogène, BERBA · 100 bandelettes
  • URPH0029MicroalbuPHAN LAURADensité, Microalbumine, Créatinine, CPERBA · 50 bandelettes
  • REG00053UrinormContrôleERBA · 2x(3x15 mL)
  • 3002Medizym Anti TPOGeneric Assays · 96 Tests
  • 3102Medizym Anti TgGeneric Assays · 96 Tests
  • 3505Medizym TRA humanGeneric Assays · 96 Tests
  • MY00405BioCLIA-SubstrateHOB Biotech · 4 X 600 Tests
  • MY01312Conjugate and Microparticle Reagent KitHOB Biotech · 150 Tests
  • MY01315Calibrator and Control SetHOB Biotech · CAL:0.5mLx7; CON:1mLx2
  • TOP-WBGMTOXOPLASMA WB IgG-IgMLDBIO · 12 / 24 / 96 tests
  • TXA-WBGTOXOCARA WB IgGLDBIO · 12 / 24 / 96 tests
  • LES-WBGLEISHMANIA WB IgGLDBIO · 12 / 24 / 96 tests

The search covers three fields at once: the reference, the short label and the long description. Type XSYS for the reference, H360 for the label, créatinine for the description. The brand is not part of the searched text: on the production site, it is a separate facet, like the category.

Mechanism rebuilt for this site, not a screenshot of the product. Rule taken from src/components/catalogue/CatalogueClient.tsx. 24 real references from the public catalogue, out of the 418 online.

From the interface down to the data

  1. 01

    Interface

    Two route groups - French at the root, English under /en/. A shared src/views layer avoids duplicating any logic between locales.

  2. 02

    Typed content

    The catalogue is TypeScript, not a database: 418 entries across 21 sections, versioned in git, checked by the compiler, at zero runtime cost.

  3. 03

    Server functions

    Supabase Edge Functions with a _shared layer: token-bucket rate limiting, JWT verification, CORS, email sending. No secret in the bundle.

  4. 04

    Delivery

    Static export deployed by incremental SFTP to OVH, with an Apache configuration carrying redirects, security headers and CSP.

Engineering decisions

The choices worth defending, and why.

  • 01

    A static site is not a poor site

    The project moved from Firebase + Vercel to Supabase + OVH shared hosting, as a full static export. That removes any application server to maintain: only HTML, CSS and JavaScript remain. The trade-off is real - no more API routes in the application - and that is what made the migration interesting: all the server logic had to be redesigned as Edge Functions, with a much clearer boundary between what is public and what is not. Deployment is a Node script doing incremental SFTP. The rest fits in an .htaccess: 301 redirects, forced HTTPS, security headers, and a rewrite fixing Next's prefetch paths - the classic trap of static export on Apache.

    • next.config.ts
    • scripts/deploy-ovh.mjs
    • public/.htaccess
  • 02

    The compiler guarantees no translation is missing

    No i18n library. The English dictionary derives its type from the French one: a forgotten key becomes a TypeScript error at build time, never an empty string in production. The same principle protects URLs - a single function decides whether a page is translated, and it drives the links, the language switcher and the sitemap at once. So it is structurally impossible to advertise an English URL that would return a 404. French stays at the root of the domain: English is added without breaking a single existing URL.

    • src/i18n/config.ts
    • src/i18n/index.ts
    • app/sitemap.ts
  • 03

    A security layer that survived a platform change

    The token-bucket rate limiter written for the Next routes was ported as is into the Supabase Edge Functions, alongside JWT verification and role checks. That is the test that counts for a so-called reusable building block: it changed runtime without changing shape. A function's processing order stays the same - CORS, rate limiting, parsing, validation, authentication, business action - and that order is not cosmetic: validating before rate limiting hands an attacker the cost of parsing for free.

    • supabase/functions/_shared/ratelimit.ts
    • supabase/functions/_shared/auth.ts
  • 04

    The catalogue translation is derived, not copied

    Translating 418 sheets by hand guarantees divergence at the first update. A script regenerates the English catalogue by substitution through a translation table: the English version is a product of the French one, not a copy ageing next to it. The same pipeline produces the printable PDF catalogues.

    • scripts/catalogue-i18n/build_en.py
    • scripts/catalogue-print-*.mjs
  • 05

    Animations driven by markup, zero JavaScript per page

    A component with no output, mounted once in the layout, observes the document and animates the whole site: scroll reveals, animated counters, parallax smoothed by interpolation. Adding a class is enough to animate an element. A mutation observer picks up dynamically added nodes, and everything is cleaned up on unmount.

    • src/components/RevealObserver.tsx

Tech stack

  • Next.js 16
  • React 19
  • TypeScript
  • Tailwind v4
  • Supabase
  • Edge Functions
  • OVH
See the service

A similar project?

Logbook

In the logbook

Other projects