Case study · 03 / 07

CTREQ Blog/Archive

Institutional Archive Section

Fig. 01 — CTREQ Blog/ArchiveHover for colour

Secondary section of the CTREQ website dedicated to archiving past institutional projects and RIRE articles (3–5 years old). Headless React + WPGraphQL architecture with automatic age-based filtering and a minimal design that keeps the content hierarchy intact.

The CTREQ Blog / Archive is a secondary section of the CTREQ website built to preserve the history of institutional projects and older RIRE articles. During the full redesign of the main site, CTREQ's leadership wanted only recent, strategic content in the spotlight. Older projects and articles more than three years old (up to five) had to stay accessible, but in a deliberately minimal space that would not pull attention away from the main site. I therefore built a headless archive page, connected to the same WordPress as the main site, with advanced age-based filtering logic (CTREQ + RIRE). The look is intentionally plain and neutral to reflect its role: an institutional archive, not a flagship product. It runs on a modern React and WPGraphQL architecture with optimised handling of content coming from several sources.

Main Features

Technical Challenges

Technologies

Year

In the wild

Live captures · hover for colour

What it does

01Displays older CTREQ projects no longer shown on the main site

02Displays older RIRE articles (between 3 and 5 years old)

03Automatic date filtering to separate recent content (main site) from older content (archive)

04Unified headless architecture: one WordPress, two front-end behaviours

05Single WPGraphQL endpoint for CTREQ projects

06Second WPGraphQL endpoint for RIRE articles

07Multi-source data merging in React

08Minimal interface (deliberately pared-back UX)

09Intentionally limited SEO so it does not compete with the main site

10Simple, fast pagination

11Dedicated article / project pages (details + full content)

How it was solved

01Unifying two heterogeneous WordPress sources (CTREQ + RIRE) into a single archive

02Handling two distinct time rules: CTREQ (active vs archived projects) and RIRE (3 vs 5 years)

03Content normalisation: formats, fields, metadata

04Neutral design and optimised performance without affecting the main site

05Deliberately limiting this section's SEO without blocking indexing

06Automatic age-based sorting (date-based filtering)

07Front-end merging of multiple GraphQL endpoints

08Stable rendering despite differing WordPress schemas

Stack

Front-end

Back-end

Tools