domain-strategy

# Domain Strategy Decide how domains, subdomains, and DNS work across a portfolio. Stack-agnostic. Works for one site or one hundred. --- ## When to use - Setting up DNS for a new site (apex vs www, primary vs aliases) - Choosing or switching registrars - Planning redirects across multiple domains (parked, retired, consolidated) - Deciding subdomain vs subfolder vs separate domain for a new product line - Consolidating multiple sites into one - Splitting one site into multiple - Setting up DNS for email, security records, third-party services ## When NOT to use - Migrating content between platforms with URL changes (use `content-migration`) - Email authentication setup specifically (use `email-deliverability`) - Security headers or HTTPS config (use `security-baseline`) - Internationalization domain choices (use `internationalization`) --- ## Required inputs - Current domain inventory (every domain you own or operate) - Status of each (live, parked, redirected, retired) - Strategic role of each (primary brand, sub-brand, defensive registration, campaign) - Current DNS provider and registrar for each - Email and third-party service dependencies --- ## The framework: 5 decisions Every domain decision falls into one of these buckets. Address them in order. ### Decision 1: Apex vs www as canonical Pick one. Redirect the other to it. Pick before launch. Changing later is painful. - **Apex (example.com):** cleaner, more memorable, the modern default. - **www (www.exa...