Dual corporate & research marketing sites
Energy Corporate Sites
Paired Next.js sites for S-Oil Corporation Pakistan—product-heavy corporate brand presence and a research/lab sister site with static TypeScript content modules.
Background & Context
s-oil is a monorepo of two independent Next.js marketing sites for S-Oil Corporation Pakistan (parent: Total Lubricants Pakistan Pvt. Limited): s-oil-corporate/ (brand, products, industries, blog, partners, careers, technology) and s-oil-research/ (research & laboratory division). Both use App Router + TypeScript + Tailwind 4 + React 19 + Next 16.2.9. Content lives in TypeScript data modules—no CMS, API routes, or database in either package.
One generic site could not serve both institutional buyers evaluating lubricants and research-focused visitors seeking lab credibility. Corporate carries a product catalogue (passenger-car, motorcycle, diesel, gear-oil, treatment) with specs and datasheet/MSDS/shop URLs pointing out to shop.soillubricants.com. Research covers laboratory and research narratives with a link back to https://s-oil.pk.
Contact, partner, and career forms are client-side success UI only (setSubmitted(true)—no fetch). Corporate optional Google Analytics via NEXT_PUBLIC_GA_ID; sitemap builds from static paths + products + blog posts.
The Challenge
An energy lubricants organization needed distinct digital surfaces for corporate credibility and research storytelling—without diluting either message or over-building a CMS/backend for static brand content. Without a coherent dual corporate & research marketing sites foundation, Energy Corporate Sites stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Tekvers delivered two coordinated Next.js 16 experiences sharing brand discipline via adapted data/company.ts modules while specializing IA: a product-heavy corporate site and a lighter research/lab site. Tekvers delivered a maintainable dual corporate & research marketing sites system for Energy Corporate Sites using Next.js 16, React 19, TypeScript, Tailwind CSS 4, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Audience-split information architecture
Corporate journeys prioritize products, industries, technology, partners, careers, and blog; research journeys prioritize About, Laboratory, Research, and Contact—so neither audience hits the wrong depth first.
Static typed content model
Products, blog posts, industries, company pages, and research stats live as TypeScript modules—marketing teams update data files without a headless CMS dependency.
Shared brand, specialized layouts
Duplicated/adapted company data keeps naming and corporate URL consistency; corporate adds carousel, WhatsApp float, and richer product/blog UI while research stays a focused multi-page companion.
What We Delivered
- Corporate Next.js site: home, about, products (+ slug), industries, technology, partners, blog (+ slug), careers, contact, company pages
- Product catalogue data with category SKUs, specs, and datasheet/MSDS/shop links
- Research Next.js site: home, about, laboratory, research, contact
- TypeScript content modules for company, products, blog, industries, and research
- Client-side contact/partner/career form UIs
- Corporate sitemap generation and optional GA integration
- WhatsApp floating contact on corporate; cross-link to s-oil.pk from research
Outcomes & Impact
- Clearer institutional messaging for lubricant buyers and partners
- Dedicated space for research/lab narratives
- Cohesive multi-site brand presence without a shared backend
- Maintainable static content structure for marketing updates
Stakeholders find the right S-Oil story fast—corporate visitors see products and credibility; research audiences get laboratory depth—on a maintainable Next.js pair that does not invent CMS or e-commerce checkout inside these marketing apps.
Technology Stack
Services Delivered
Related Case Studies
Guides & articles from this niche
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.