Back to work

Fernmark

Upgrading a licence programme website in phases, while keeping existing pages working and giving editors control of content.

Client
NZ Story Group
Timeline
Q4 2025 – Q1 2026
My role
Technical Leadership, System Design, Frontend Development, CMS Integration, DevOps & Deployment
Built with
Next.js, Drupal, Tailwind CSS
Website
Visit website ↗

What changed

Silver fern fronds in native New Zealand bush

Overview

The NZ Story Group needed updated pages and a way to manage content without relying on developers. We rebuilt the selected pages while preserving the rest of the site.

The business need

FernMark serves businesses exploring New Zealand’s licence programme and existing licensees. The website needed updated pages, but a full rebuild would have exceeded the agreed scope and budget.

The NZ Story Group also needed to make routine content changes without sending each update to a developer.

My responsibility

I led the technical approach, project setup and deployment pipeline, working alongside the development team on the rebuild.

We agreed to update selected pages and preserve the rest of the site. That decision kept the project within scope and avoided a migration of every existing template.

Editing after handover

Drupal holds structured content and Next.js renders it. Editors assemble pages from reusable blocks with defined fields.

The editing experience gives the team control over content without asking them to manage page markup. Each block has a matching frontend component.

The migration decision

New pages needed a newer Tailwind CSS version. Legacy pages depended on an older version with different classes and configuration.

I separated the style builds so both could coexist. We could deliver the agreed pages and leave a path for the remaining pages to move later.

Planning a similar project?

Send your existing URL and what needs to change. We can start by defining the scope.

Discuss your project

Next project

YuNet