Museum Kiosk & CMS

QOGLR

A touch-first museum kiosk and content management system designed for an interactive visitor experience, with structured historical content, galleries, media management, and performance-focused delivery.

QOGLR project
01 — Overview

Project details

An interactive museum kiosk and CMS created for presenting Gurkha and historical content through a touch-first visitor experience.

Year2026
RoleFull-Stack Engineer
TypeMuseum Kiosk & CMS
WebsitePrivate
02 — The problem

The challenge

A kiosk application has different constraints from a normal website. Visitors need immediate feedback, readable content, simple touch interactions, and reliable media delivery. At the same time, administrators need a practical CMS for managing structured historical content and media.

03 — The approach

How I approached it

I worked on the public kiosk experience and the administrative CMS, with an emphasis on touch interaction, structured content, media management, and fast rendering. The architecture also considers caching because the kiosk should avoid unnecessary repeated work during visitor sessions.

Project interface and system overview
04 — Engineering

Engineering breakdown

The important parts of the project were not just the interface, but the systems and decisions behind it.

01

Designing for touch

The interface is designed around a kiosk rather than a traditional desktop website. Navigation, typography, spacing, horizontal timelines, and interactive areas are considered for touch interaction and fixed display environments.

02

Structured historical content

The CMS provides structured content that can be managed independently from the presentation layer. This allows historical pages, regiment information, galleries, and other sections to evolve without rebuilding the entire interface.

03

Media delivery

The system uses Cloudinary for media management and direct uploads, with upload constraints designed to prevent unnecessarily large assets from entering the system.

04

Performance for a kiosk environment

Unlike a normal website where users may visit once and leave, a museum kiosk can serve many consecutive visitors. Caching and efficient rendering therefore become part of the product experience rather than an afterthought.

05

Key engineering work

  • Touch-first kiosk interface
  • Museum content management system
  • Structured historical content
  • Gallery and media management
  • Cloudinary media uploads
  • Responsive kiosk layouts
  • Performance-focused delivery
06

Key decisions

  • Treat the kiosk as a dedicated product rather than a normal website.
  • Separate structured content from presentation.
  • Use managed media delivery instead of serving large raw assets directly.
  • Design caching around repeated kiosk usage.
07

Results

  • Created a reusable CMS-backed museum presentation system.
  • Made historical content manageable without changing application code.
  • Established an architecture suitable for a continuously running kiosk environment.
08

What I learned

  • The physical environment where software runs should influence architecture and UX decisions.
  • Performance requirements are different when the same device serves hundreds of sessions.
  • Content structure matters as much as visual presentation for long-lived informational products.
09 — Stack

Technologies

Next.jsTypeScriptReactPrismaMySQLTailwind CSSCloudinaryNext.js App Router
10 — Visuals

Project gallery

Selected visual highlights from the QOGLR project.

Project screenshot 1
01
Project screenshot 2
02
Project screenshot 3
03
Project screenshot 4
04
Next project

Have a problem
worth solving?

Whether you're building something new or improving an existing system, let's talk about the problem and what it would take to build it well.

Start a conversation