ITU Docs

Introduction

What the ITU platform is and who it's for.

High-level architecture

The platform follows a three-layer pattern:

  1. Content sources — multiple WordPress installations (each with a headless REST plugin), Payload CMS for structured content, and external data feeds (publications, country data, etc.).
  2. Gateway API — a Hono-based API layer that normalises, caches, and aggregates responses from every backend into a single contract the frontend can rely on.
  3. Next.js frontend — a single App Router application (apps/web) that renders pages using data from the Gateway and a shared component library (@itu/ui).
WordPress (x5+)  ──┐
Payload CMS       ──┤
Publications API  ──┼──▶  Gateway API  ──▶  Next.js frontend
Country data      ──┤
Image service     ──┘

Who is this documentation for?

This docs site serves two primary audiences. Use the top-level navigation to find the section most relevant to you.

  • Developers — engineers working on the frontend, gateway, CMS, or WordPress plugins. You will find architecture guides, API references, design-system tokens, and package documentation in the Developers section.
  • Content managers — editors and administrators who author and publish content through WordPress or Payload CMS. The Content Managers section covers workflows, block types, and publishing best practices.

Next steps

Quick Start

Clone the repo and run the dev servers in under five minutes.

Repository Structure

Understand how the monorepo is organised.

Architecture Overview

Deep dive into the system topology and data flow.