Oppenheimer · author's website
An author's website to explore like a library.
Read the case studyCase study · Production deployment
A Next.js environment for an urban art platform.
RTZM already had a developed Next.js application. We set up its production environment and update process, from the code repository to the public website, with checks after each release.
The starting point
The project context.
RTZM is an urban art platform bringing together a gallery, artist pages, shop, iARTzm experience, news and investor journey. Our work covered deploying this existing application to production and its update process.
Client website
An art platform with several public journeys.
The website needs to support discovering works, artist profiles, the shop, iARTzm experience, news and project-related enquiries.
The challenges
What needed to be addressed.
- 01
From code to a public website
A Next.js application can evolve successfully in a repository without being straightforward to operate in production. The transition between code, build, publication and visible checks needed to be structured.
- 02
Automating without exposing the system
The workflow needed to reduce manual update steps while keeping infrastructure details and internal procedures out of public view.
- 03
Preserving a distinctive website
The website has a strong artistic identity: typography, visuals, gallery, shop and animations need to remain consistent after each technical change.
What we did
The work, step by step.
Analysed the Next.js application foundation, public routes and production requirements.
Set up a runtime environment adapted to an already developed Next.js application.
Clearly separated the code repository, production build and publicly served website.
Configured an update process from the repository to the public website to reduce repetitive operations and omissions during releases.
Checked key pages, navigation, visuals, public metadata and website responses after launch.
Provided technical support to keep the application publishable, verifiable and easier to take over after changes.
Operations
An environment designed to publish without starting over.
The process connects the code repository to the public version: building, publishing and checking pages after each change.
Next.js application
The website uses a Next.js application with public pages, navigation, animated components and content organised around several journeys.
Update workflow
The process connects the code repository to the public website so changes can be published reproducibly, with fewer isolated manual steps.
Production checks
After launch, checks cover website access, navigation, images, key pages and public signals useful for SEO.
For visitors
What you find when you arrive.
- 01
A clear proposition from the homepage
The homepage presents urban art, exhibitions, AI-assisted generation and initial calls to action for discovering the project.
- 02
Separate journeys
Gallery, artists, shop, iARTzm, news and investor page avoid assigning every intention to a single page.
- 03
A visual identity to preserve
Artworks, typography and animations directly contribute to the platform’s credibility. The technical environment needs to preserve this appearance through changes.
Who visits, and why
Collectors and art enthusiasts
Discover the RTZM world, explore artworks, view artists and move towards exhibition or shop areas.
The RTZM team
Have a website published within a more stable technical framework, with a clearer transition between code changes and the publicly accessible version.
Partners and investors
Quickly access positioning, introductory pages, news and contact points explaining the project.
What the project delivers
An application that is easier to operate.
The items below describe the functions and documented work for this project. They are not measurements of traffic, enquiries or revenue.
- 01
A defined publication process
Updates follow the configured process between the code repository and public version.
- 02
Update steps brought together
The process brings update steps together and includes post-publication checks.
- 03
A better-supported website
The platform can continue presenting its identity, artworks, artists and public journeys with a clearer technical framework.
Explore further
Related case studies.
Bikourim
An association's website brought to life from its logo.
Read the case study
Ava Films
A film website that tells a story.
Read the case studyOur services