Case study · Multi-brand platform

Visit Marco Island

Sister guide to Visit Naples, served from the same codebase and the same deploy. Its own brand, its own "Ask Visit Marco" assistant, and its own events network.

Second brand, same codebase
Its own assistant, tuned for the island
Events that never mix with Naples

RoleCo-owner, publisher & engineerRegionNaplesNext.jsSupabaseClaude APICloudflare Workersgovisitmarcoisland.com ↗

The point

Marco Island is the proof that the Visit Naples platform is really a platform. There’s no fork and no second codebase. The same Next.js app reads the hostname and becomes a different publication.

What’s different on Marco

Brand and content. Its own logo, navigation, guides and listings: beaches, shelling, boat tours, charters and stays.
Ask Visit Marco. The same assistant with island-specific prompts. It suggests “shelling near Tigertail Beach,” not “happy hour downtown.”
Its own events network. Marco gets its own edition of the events platform, Events Marco, with island venues, the city and the chamber. Naples, Bonita and Fort Myers share events with each other, but Marco events never mix with them.

Events Marco homepage — Events Marco feeds the Visit Marco Island events pages. Same engine as Events Naples, separate network.

Visit Marco Island on a phone — Events Marco feeds the Visit Marco Island events pages. Same engine as Events Naples, separate network.

Why it matters for clients

Multi-brand, multi-location and franchise businesses usually pay for every site twice: once to build it and again every time something changes. With one codebase serving every brand, each new location is configuration, not a project.