Overview
The Challenge
One website for a gallery with many front doors.
The Slovak National Gallery is the country's national art institution, operating under the Ministry of Culture of the Slovak Republic, with five galleries across Slovakia, including the Slovak National Gallery in Bratislava, Zvolen Castle and Mansion Strážky.
SNG is not one building. Each gallery has its own opening hours, address, exhibitions and programme, and visitors arrive looking for one specific place. The previous site did not reflect that.
SNG's Department of Digital Collections and Services wanted a new platform that would make the gallery easier to visit, simplify the information architecture and connect content that lived in separate places. Its in-house digital team already ran a strong product practice, with a product manager, its own developers and a UX/UI designer working in Figma. What it needed was senior development capacity that could work inside its process rather than replace it.
The tender set clear technical expectations:
A modern frontend (TypeScript, Vue.js, Tailwind CSS) on a Laravel backend
Automated CI/CD, static checks and tests
Accessibility in line with WCAG 2.1 AA and Slovak public-sector web rules
Protection against standard attacks such as XSS, CSRF and SQL injection
All code published to SNG's own Git repository
How We Worked
Working as part of SNG's team.
We worked in sprints planned and estimated together with SNG, as an extension of its in-house team.
The Platform
A platform built around galleries.
The core idea was the workspace: every gallery is a workspace with its own opening hours, address, GPS location, social links and footer. Exhibitions, events and pages are assigned to a workspace, and the site adapts to the gallery a visitor has chosen.
What We Built
A live status that reads each gallery's opening hours.
Exhibitions and events with two levels of filtering, by category and by time period.
Curators, exhibiting artists, related events, an info box with hours and prices, and exhibited works in a lightbox.
Linked from exhibitions, events and the main navigation.
A megamenu, a gallery switcher and a full Slovak and English version.
Workspaces, promo texts, site-wide notices, price list templates, redirects, user permissions and media management with automatic image processing.
Launch and Beyond
Growing the platform after launch.
Before launch we optimised page speed, worked through accessibility fixes, set up server-side rendering, automated production deployment with GitHub Actions, and connected analytics.
After the new site went live, SNG commissioned two more rounds of work:
Service and development (2023–2024). A 12-month contract combining SLA support with development capacity for new features, released through December 2023. From then on, SNG's own developers built new features, with BRACKETS reviewing their pull requests and consulting on request.
Ongoing support (2024–2025). A 12-month SLA covering hosting, monitoring, error tracking and incident response, plus change requests such as school group reservations, collection detail adjustments and a Google Tag Manager data layer.
The Handover
A clean handover.
In 2025, SNG took the platform fully into its own hands. We handed over source code, repositories, configuration, technical and user documentation and the full record of changes and deployments. Because the code had lived in SNG's repository all along, the handover was a formality rather than a migration.
The Results
A new sng.sk, live in 2023.
The rebuilt site went live within the first contract, including production setup and automated deployment.
One site that works for all five galleries. Visitors pick a gallery and see its hours, programme and directions. Editors manage all of them from one admin.
Exhibitions are easier to explore and to visit. Filters, rich exhibition pages and ticket links sit on every relevant page.
A platform SNG kept building on. The first project led to two more contracts and almost three years of continuous work.
Full ownership stayed with SNG. The gallery holds its code, documentation and infrastructure knowledge, and now runs the platform itself.
FAQ
In Production
Related
Need senior developers inside your team?
Let's talk