Cyclist in Motion
Cyclist in Motion

SELECTED CASE STUDY

Szegedi Nemzeti Színház

Szegedi Nemzeti Színház

TECH STACK

Next.js, Nest.js

YEAR

2025

Digital Theatre Platform & Custom CMS

We designed and developed a custom digital platform for Szeged National Theatre, combining a modern public-facing website with a dedicated administration and content-management system.

The platform supports programme publishing, repertoire management, news, performer profiles, galleries, promotional content and ticket-oriented user journeys, all built around reusable structured data rather than static pages.

The Challenge

A theatre website is more than a collection of static pages. Programme information changes continuously, performances are time-sensitive, and audiences need to quickly discover relevant events while the internal team needs to update content without relying on developers.

The platform therefore had to support complex theatre-specific content, frequent editorial updates, programme filtering and controlled administration workflows within a single maintainable system.

The Solution

We developed the platform as a full-stack application with a Next.js frontend and NestJS backend, supported by a purpose-built administration layer.

The public platform and CMS share the same structured content model, allowing programme entries, productions, performers, news and promotional content to be managed centrally and reused across different parts of the website.

The solution includes:

  • Responsive public website

  • Custom administration and CMS

  • Programme and repertoire management

  • Performer and company profiles

  • News and editorial publishing

  • Advanced programme filtering

  • Role-based access control

  • Gallery and media management

  • Newsletter subscription flows

  • Ticket-purchase entry points

  • S3-compatible media storage

  • Documented REST APIs with Swagger

Programme & Repertoire

A central part of the platform is the programme system.

Visitors can browse performances and filter them by criteria such as genre, actor or director, subscription or pass, date and ticket availability.

Production pages combine performance dates with structured information including cast, creative team, duration, galleries and related content, creating a consistent experience across the entire repertoire.

Custom Editorial CMS

The administration platform enables theatre staff to manage everyday content without developer involvement.

Editors can create and maintain programme entries, productions, news, banners, promotional content, performers, galleries and other website content through dedicated workflows.

Access is controlled through role-based permissions, supporting different levels of administrative responsibility.

Structured Content Architecture

Rather than treating every page as an isolated piece of content, the platform is built around reusable domain entities.

Productions, performers, roles, performance dates and editorial content are connected and reused throughout the website, making the system easier to maintain and extend while reducing duplicated content.

Technical Architecture

The platform uses a separated frontend and backend architecture.

Frontend
Next.js, React, TypeScript, Tailwind

Backend
NestJS, TypeScript, REST API, Swagger

Infrastructure & Media
Docker, S3-compatible object storage

Access Control
Authentication, roles and granular RBAC permissions

Results

The new platform gives the theatre team greater control over everyday publishing while providing visitors with a clearer way to discover performances and productions.

Key outcomes include:

  • Independent editorial content management

  • Structured and reusable theatre data

  • Advanced programme discovery and filtering

  • Integrated ticket-oriented user journeys

  • Centralized management of performers and productions

  • Maintainable full-stack architecture prepared for further development