FIX Partner
A company website rebuilt around editable content and its existing blog.
Visit FIX Partner
At a glance
- What it is
- A company website with service pages and a blog that the company's own editors update.
- My role
- Solo freelance designer and developer, with coding agents assisting under my review.
- What I built
- Migration of 14 pages and 135 posts with media and metadata
- AI SEO suggestions that keep an editor's own changes
- Server setup and deployment with Docker and Nginx
- Stack
- Next.js
- React
- Payload CMS
- MongoDB
- Docker
- Nginx
- Status
- Delivered in 2025 fixpartner.co
I designed the site and owned the architecture, code review and client revisions, while coding agents assisted with implementation. After launch, the client could keep publishing through the CMS.
What people use it for
FIX Partner already had a company website and a substantial blog. The rebuild had to preserve that material while giving the client pages they could edit and keep publishing. I handled the design and implementation solo, including the server setup and launch.
Preserve
Account for existing pages, posts and media.
Rebuild
Move the content into editable page structures.
Verify
Review the migration and check the released website.
The blog was part of the rebuild
The migration covered 14 pages and 135 posts. A new homepage would only solve part of the problem if the articles, their media or their existing routes disappeared. The content needed to fit the rebuilt site and remain available after the move.
I designed and implemented the replacement with Next.js and Payload CMS. The migration brought the articles, media and metadata into the new editing workflow, with acceptance checks against the existing content.
Give content editors a usable structure
The company needed to maintain service pages and publish articles without changing application code. Shared page structures kept related content consistent, while the CMS gave editors a place to manage it.
The editor also includes AI suggestions for SEO metadata. Editors can override those suggestions. Their deliberate changes need to survive a later save, so the workflow distinguishes a human edit from a value filled by the suggestion system.
Own the decisions through release
Coding agents assisted my implementation. I owned the design decisions and code review, checked the content migration and revised the site through client feedback. I also set up the server and deployed the application.
Before launch, I checked the agreed behavior and content and verified the production website. The client could then continue publishing through the CMS.
14 pages and 135 posts carried forward
The delivered website preserved 14 pages and 135 posts and gave the client editable pages and a blog in Payload CMS. I handled design, implementation, server setup and launch, with coding-agent assistance under my review.
The migration totals describe the original delivery. The live blog has continued changing since then.
A new website. The old posts come too.
Implementation notes
Content and delivery stack
The website uses Next.js 15, React 19 and Payload CMS 3 with MongoDB. The migration transformed WordPress content for the new CMS, including posts, media and metadata. Docker and Nginx support the deployment.
SEO suggestions with human overrides
Google Gemini supplies metadata suggestions in the editing workflow. Override detection keeps an editor's chosen values from being replaced by a subsequent automatic suggestion.
Reading the performance result
A PageSpeed comparison dated 29 December 2025 recorded mobile scores of 17 before and 94 after, and desktop scores of 47 before and 99 after. These are historical laboratory results for the homepages. They do not establish today's performance, search ranking, sales or real visitors' loading times.