AIGEMSTEK
IT Head mandate across website, CMS, deployments, and support
IT Head ownership for a consulting platform
I serve as IT Head for AiGemsTek, owning the company website and broader IT-linked mandates across web operations, platform support, deployments, access, and internal technology workflows.
The consulting firm publishes constantly — new service framings, sector lenses, and leadership notes. The site is CMS-driven so the team can push copy and structured pages without touching code.
Hero headline, strategy card, stats row, “Think global, act local” callout — all typed Payload collections rendered at build/edge time.
Typed Payload collections
Each service card — Factory Setup & Project Management, Corporate Services, Human Resources Management, Sourcing & Supply Chain, India Market Entry & Strategy, M&A, Commercialisation, Energy / EPC / Technology Advisory — is a typed Payload entry on PostgreSQL.
Adding a new sector or service is a content task, not a code task. The consulting team owns publishing end-to-end.
Architecture
- Next.js App Router, TypeScript strict, Tailwind.
- Payload CMS on PostgreSQL — typed collections for services, sectors, leadership, capability briefs, corporate profile downloads.
- Inquiry capture: typed contact form → Payload → admin queue with role-gated approvals.
- User + admin dashboard routes (register, login, role promotion). Branded loading screen for first-paint quality.
- Ongoing IT Head ownership for website reliability, CMS/content operations, hosting/deployment support, access control, and related company IT mandates.
- Deployed on Vercel.
Production baseline — SEO, security, a11y
- SEO — programmatic sitemap, canonical URLs, per-route OG cards,
Organization+ServiceJSON-LD shipped at build time. - Security headers baseline — CSP, COOP/COEP, referrer-policy, frame-ancestors.
- A11y — focus order audited, contrast ratios checked across the palette, keyboard-only nav usable.
- Component primitives —
PageShell,HeroCard,FeatureGrid,LeadershipRow— shared between marketing and admin surfaces so the editorial tone stays consistent.
What I learned
- CMS-driven beats code-driven for consulting sites. The team publishes faster than any engineer can keep up.
- Typed CMS collectionssave weeks of “what does this field mean” conversations.
- Branded loaders signal quality at first paint — cheap to build, high return on perceived polish.