Skip to content
AMTEXConsulting

Case study · Professional Services

A web platform for Amrelia Technologies with a content layer that outlives the CMS

The public site for Amrelia Technologies, an India-based digital product engineering company and AMTEX's engineering partner: a distinct editorial brand, service and case-study pages, careers with an application API, and a content model that any headless CMS can feed later.

Client
Amrelia Technologies
Industry
Professional Services
Solutions
Application Development
Technology
Next.jsReactTypeScriptTailwind CSSVercel

Challenge

Amrelia Technologies needed a site that positioned engineering, product thinking and Oracle Cloud implementation without the tired offshore vocabulary, that looked nothing like AMTEX's own site, and that would not need rebuilding when the company adopts a CMS.

Solution

The site shares its invisible plumbing with AMTEX's: a typed content contract, a repository that pages import from, local JSON today and swappable providers for a headless CMS tomorrow, and gating that hides unapproved content in production. Everything visible is different: warm paper backgrounds, an indigo-to-aqua gradient, editorial asymmetric layouts, a floating header and a different type system.

  • Service pages with flow diagrams and process timelines, including an Oracle Cloud Implementation specialism.
  • Contact and job-application routes with shared validation, a honeypot, per-IP rate limiting and pluggable delivery.
  • Structured data for the organisation, services, articles and job postings; sitemap, robots rules and generated social images.
  • Accessibility and contrast checked against WCAG AA, with reduced-motion fallbacks for every animation.

Business impact

Two companies, one engineering pattern, two unmistakably different brands. Amrelia Technologies can publish services, work and roles from data, and move that data into a CMS by writing one provider rather than rebuilding pages.

Key takeaways

  1. 01Share plumbing between sites, never the design.
  2. 02Make the content contract the product; the CMS is an implementation detail.
  3. 03Gate unapproved content in code so launch does not depend on an editorial sweep.

Facing something similar?

We will walk you through how we approached this one and what would be different for you.