Content platform
Batavia Stad
Frontend work on an existing Next.js platform, shipping CMS-driven features with GraphQL, Contentstack, and reusable components.
- Role
- Frontend developer implementing features independently and with another developer
- Key work
- CMS-driven pages, GraphQL data, and reusable Next.js sections.
- Stack
- Next.js, Storybook, Contentstack, GraphQL
- Link
- Live site
Focus
A content-driven retail destination site where page content, GraphQL data, and reusable components all needed to stay in step.
Challenge
I joined after the project was already well underway, so the first job was to understand the architecture, the component patterns, and how content moved through the CMS without slowing the team down.
Contribution
- Implemented new features in an existing Next.js codebase.
- Worked with Contentstack and GraphQL to support CMS-driven pages and reusable sections.
- Delivered pieces independently while also pairing with another developer when the work benefited from it.
- Followed the existing project patterns so new work felt like part of the platform, not an add-on.
Outcome
The project showed I could enter an established React codebase, learn its patterns quickly, and keep useful features moving without disrupting the workflow.