NCITY AVM Digital Platform

Challenge

Information about shops, campaigns, events, services and media changes regularly. Routing every update through the development team caused delays and unnecessary work. At the same time, incomplete or incorrect changes needed to be kept off the public website.

Solution

I structured the platform so that the editorial team can make routine updates through its own administration system. Shops, campaigns, events, services, media files and static pages are managed as separate content types.

The publishing process has four steps:

1. Content is prepared in the content-management system.
2. The editorial team reviews the changes.
3. An authorised user approves them.
4. Approved content is published to the public website.

This allows the editorial team to work more quickly without giving up control over publication.

My contribution

I structured the requirements, developed the content model and designed the publishing workflow. I also tested the main flows between the administration system and the public website, and coordinated implementation and handover.

I used AI-assisted tools during implementation. The product approach, architectural decisions, tests and release approval remained my responsibility.

Outcome

The editorial team can manage shops, campaigns, events and other content without code changes. Publications pass through a defined review and approval process. The platform is live at ncityavm.com.

Technologies

Next.js · Payload CMS · PostgreSQL · Cloudflare Pages · GitHub Actions · Docker · S3-/R2-compatible media storage

This page contains only information about architecture and workflows that can be shared publicly. Client data and internal operational information are not published.