Delivered projectWeb DevelopmentFull website + visual CMSDavid Demid

DavidDemid.com - a complete consultancy platform

I designed and developed my consultancy platform end to end: positioning, responsive pages, reusable sections, an editable CMS and a clear path from expertise to a project conversation.

Client
DavidDemid.com / my own consultancy platform
Period
Initial build October 2026 / Sanity migration November 2026
Contribution
End-to-end website strategy, UX, visual design and development
Current DavidDemid.com project homepage with a portrait and growth consulting positioning

Delivered result

A responsive consultancy website with structured service pages, case studies, insights, reusable conversion sections and protected contact forms. The current DDN build uses Sanity CMS and Visual Editing with Next.js on Netlify.

The result

I built a complete website around the way I work: connect acquisition, conversion and commercial data, then turn that expertise into a clear offer. The result is a reusable content and conversion system spanning services, industries, case studies, insights, about and contact.

I owned the project from positioning and page architecture through visual design, component implementation, content schemas and interaction QA. This case presents the current DavidDemid project developed in DDN.

A clearer route from expertise to a conversation

The homepage establishes the offer quickly, gives visitors two clear next steps and introduces services through distinct color-coded blocks. Each service has its own supporting page, related expertise and a consistent discussion CTA.

DavidDemid.com desktop screenshot of the current consultancy homepage

DavidDemid.com desktop homepage, captured on 8 October 2026: positioning, portrait and primary actions.

Cases show project context, my contribution and the delivered result. Insights use a separate editorial structure with dates, sources and a table of contents. Visitors can evaluate the work before opening the contact form, booking a conversation or choosing messaging.

One design system across desktop and mobile

I developed a consistent black-and-white foundation, expressive typography, sharp geometry and selective service colors. Buttons share the same interaction language instead of changing character from page to page.

The mobile experience was designed as its own layout: a right-to-left menu, larger navigation targets, service progress, a readable article TOC near the start of each case, and a contact trigger that appears after the opening screen.

DavidDemid.com mobile screenshot showing the responsive hero and primary actions

Actual 390px-wide mobile viewport. Content, navigation and portrait framing adapt to the narrower screen rather than shrinking the desktop page.

Reusable service pages and conversion sections

Services use shared components for the problem, approach, delivery and next step. That makes the offer easier to understand and keeps the site coherent as new services are added. The same contact and messaging logic is reused across the site.

DavidDemid.com desktop screenshot of the website-development service page

A service page from the same component system. Headlines, supporting copy, actions and section content remain editable.

A website I can keep editing

The technical foundation is Next.js, React, TypeScript and Tailwind, with Sanity CMS and Sanity Visual Editing. Page layouts, sections, images, links, service data, case metadata and SEO fields have explicit content models. Published pages read published CMS content; protected preview routes support draft editing without exposing drafts to ordinary visitors.

The result is practical independence: I can revise the offer, replace images, reorder supported page sections or publish a new case without rebuilding the design for each change. Cases derive their table of contents from article headings; collection cards load only the fields they need.

Netlify hosts the Next.js website. Sanity manages the current editable content; Git retains code and local content snapshots. This separates content publication from a frontend code deployment. The project originally used Git-backed visual editing before the November migration, while the October screenshots preserve the earlier visual implementation.

Contact handling and implemented safeguards

Contact submissions go through a server-side API with a field allowlist, email and metadata validation, length limits, honeypot handling, repeated-submission checks and basic per-instance rate limiting. Outbound processing supports a server-side webhook secret. Text forwarded into spreadsheets is protected against formula injection.

The form pipeline combines validated inputs, server-side credentials and spreadsheet-safe processing, giving contact handling a clear technical structure.

What I delivered

  • A finished responsive visual and component system.
  • Clear service, industry, portfolio and editorial page structures.
  • A reusable contact and messaging journey instead of inconsistent page-specific actions.
  • Schema-driven editing for content and SEO through Sanity CMS and Visual Editing.
  • Server-side form validation and abuse controls.
  • Route, editor-annotation and desktop/mobile layout checks.

The achieved outcome is an implemented, maintainable consultancy platform: a consistent offer, a recognizable design and a content system I can keep developing without losing visual coherence.

Website development, Brand positioning and Conversion optimization.

Discuss your website project.

October 2026 screenshots document the original visual build. The current repository includes the November migration to Sanity CMS and Visual Editing; these screenshots are not presented as captures of the updated editor.