A custom property website and CMS replacing WordPress

In 2025, I led the technical rebuild of a residential property's website. The existing WordPress site had become difficult for the client to maintain, had security concerns, and no longer matched the quality of the property being marketed.

A lead UX designer created the new design. I worked with them to turn it into a responsive production site and built the CMS behind it.

Why we moved away from WordPress

The client was in the middle of an active marketing drive, so this was not a background website refresh. Prospective buyers were using the site to understand the location, the homes, and the wider development.

The old site also made routine updates harder than they needed to be. The team depended on a mix of theme behaviour, plugins, and WordPress knowledge they did not have in-house. Updating one part could affect another, while putting updates off left the existing maintenance and security issues in place.

The answer was not simply “custom is more secure.” A custom build still has to be maintained properly. What it gave us was a smaller surface we could understand and control, built around the publishing work the team actually does.

A CMS for this site, not every possible site

The public website is highly visual, which made a generic page builder a poor fit. It would either give editors enough freedom to break the layouts or leave developers doing routine content updates.

I shaped the CMS around the actual content: page sections, campaign banners, property highlights, galleries, amenities, testimonials, news, sustainability articles, and search metadata. Editors can update the words and media without touching layout code, while the design stays consistent across desktop and mobile.

The public site brings together the location and master plan, homes, villas, beach lots, amenities, floor plans, virtual tours, news, and inquiry forms. All of it is managed through the same administration portal.

Keeping the administration side deliberate

I built the CMS with authenticated accounts, roles for what an administrator can view or change, inactive-account controls, server-side validation, and an activity history for administrative changes.

That gives the client a focused set of publishing tools instead of an open-ended plugin ecosystem. It also gives our delivery team one application and release process to maintain.

The result

The new site replaced WordPress and gave the marketing team control over the content they change day to day. The parts that need engineering still go through a normal release, but publishing a banner, gallery, article, or property update no longer does.