Our Cape Town WordPress projects follow a structured methodology designed to produce fast, maintainable, professional WordPress sites. Discovery and planning (week 1): understanding the business, its customers, and the website's role in the business. For e-commerce: mapping the product catalogue, understanding shipping requirements, and identifying payment gateway needs. For professional services: defining the content strategy (services, case studies, team, blog). For tourism: mapping the booking flow and identifying which booking systems to integrate. Output: a sitemap, wireframes for key pages, and a technical specification. Design (weeks 1-2): custom design — not a purchased theme with colour changes. We design in Figma: creating a visual system (typography, colours, spacing, component styles) that reflects the business's brand and resonates with its target audience. South African design considerations: colour choices that work in bright daylight (Cape Town's sunshine makes screens less readable — high contrast is essential), typography that is legible on mobile screens at various distances, and imagery that is authentically South African (not American stock photography). Responsive design: designed at 4 breakpoints (mobile 375px, tablet 768px, laptop 1024px, desktop 1440px) — not just scaled down from desktop but genuinely designed for each screen size. Development (weeks 2-4): custom WordPress theme development. We build on: GeneratePress or Kadence (lightweight theme frameworks — 30KB vs. 300KB+ for bloated themes like Avada or Divi), Gutenberg Block Editor (WordPress's native editor — using custom blocks for the client's specific content types), ACF (Advanced Custom Fields) for structured content (flexible content layouts, repeater fields, option pages), and custom post types for content that doesn't fit posts/pages (testimonials, team members, projects, properties, menu items). Plugin strategy: minimal plugins, carefully selected. Every plugin adds weight, potential security vulnerabilities, and maintenance burden. We typically use: Rank Math (SEO — lighter than Yoast), WP Rocket (caching — the most effective WordPress caching plugin), Imagify (image optimisation — WebP conversion, compression), Gravity Forms or WPForms (contact forms — with POPIA-compliant consent checkboxes), and WooCommerce (only for e-commerce sites — no installing WooCommerce for a simple contact form). Security: Wordfence or Sucuri (firewall, malware scanning), forced HTTPS, disabled XML-RPC (common attack vector), hidden login URL, and strong password enforcement. Performance optimisation (week 4): WordPress performance is where most Cape Town developers fail. We implement: server-level caching (WP Rocket + object caching via Redis), CDN (Cloudflare — with South African edge nodes, ensuring fast delivery to SA visitors), image optimisation (WebP format, lazy loading, responsive image sizing), critical CSS (inlining above-the-fold CSS, deferring the rest), JavaScript deferral (non-critical JS loaded asynchronously), and database optimisation (cleaning post revisions, transients, and orphaned metadata). Target: Google PageSpeed Insights score of 90+ on mobile — achievable with proper WordPress optimisation but rarely achieved by Cape Town WordPress sites. South African hosting: we recommend hosting on infrastructure that serves South African visitors fast. WP Engine (global CDN with good SA performance), Kinsta (Google Cloud — no SA region but excellent global CDN), Cloudways on DigitalOcean (Cape Town data centre — lowest latency for SA visitors), or Afrihost (South African hosting — variable quality but lowest latency). Load shedding consideration: South African-hosted WordPress sites on local servers risk downtime during Eskom load shedding. We configure: Cloudflare's always-on caching (serving cached pages when the origin server is down), UptimeRobot monitoring (alerting when the site goes offline), and hosting providers with generator backup (WP Engine and Kinsta's infrastructure is immune — cloud-hosted, not in SA data centres).