OPOW

Official websites for Algeria’s OPOW sports offices (Office du Parc Omnisports de la Wilaya), one per wilaya: stadiums, swimming pools and sports halls shown with photographs, capacity and contacts, plus an institutional section. Every site is bilingual — Arabic and English — and maintained by its own office. Many wilayas are deployed from one JSON-driven PHP architecture; Blida is linked here, with Algiers, Oran, Ghardaïa, Naâma and Mascara among the other examples — the same structure, each wilaya’s own palette.

Each wilaya office needed a credible official presence for facilities the public has to find, in two languages, with correct local search behaviour. There was no shared engineering team and no CMS budget — and many separate sites risked becoming many divergent codebases.

I built a single PHP architecture and deployed it per wilaya: page templates for the homepage, institutional About, facility index and facility detail, with all content in flat-file JSON so a new site is a configuration exercise rather than a rewrite. Each deployment carries its own SEO layer — dynamic canonical URLs, JSON-LD for sports facilities and breadcrumbs, sitemap, 301 redirects, gzip and cache headers.

• Per-wilaya websites

  A dedicated official bilingual site for each sports office, rolled out wilaya by wilaya.

• Facility catalogues

  Stadiums, pools and halls with photographs, capacity, structured detail pages and JSON-LD.

• Client-maintained JSON

  Facility content lives in flat-file JSON each office edits without touching templates.

• Per-site SEO layer

  Canonical URLs, JSON-LD, sitemap, redirects and cache headers shipped as part of each deployment.

• OPOW

  

  Home — Mascara

• OPOW

  

  Facility catalogue — Ghardaïa

• OPOW

  

  Facility detail — Naâma

• OPOW

  

  Institutional About — Oran

• OPOW

  

  Contact page — Blida

• 

  Mobile home — Blida

• 

  Mobile menu — bilingual toggle

1. 01.

   Copy-per-site maintenance

   Every fix ships many times by design; the content model is per-site JSON over copied code. A shared theme with per-site configuration is the correct next evolution.

2. 02.

   Fleet operations

   Independently hosted domains drift: two served a mismatched shared-hosting certificate and one was offline at last check. A fleet like this needs periodic status checks, and that process is now part of the maintenance plan.