A client designs a new experience for one of their brand sites with the following parameters: • The new experience should behave like a desktop…

The requirements point to a solution that combines a rich, app-like user experience with the need for strong SEO, fast initial load times, and WYSIWYG authoring. The AEM SPA Editor SDK with Server-Side Rendering (SSR) is designed specifically for this scenario. The SPA framework (like React or Angular) provides the "desktop application" feel with dynamic content. The AEM SPA Editor allows marketers to author the content in a WYSIWYG manner. Crucially, SSR addresses the SEO and initial page load concerns by pre-rendering the SPA on the server, delivering fully-formed HTML to the browser and search engine crawlers for the first request.

A. Using AEM as a headless CMS alone does not solve the SEO and initial page load problems inherent in client-side rendered single-page applications.
B. Traditional server-side components provide good SEO and authoring but fail to deliver the fluid, "desktop application" like experience the client wants.
D. Creating API-driven components is a part of a headless or SPA implementation but is not a complete approach; it doesn't inherently solve the SEO and WYSIWYG requirements.

1. Adobe Experience Manager 6.5 Documentation, "Developing for the AEM SPA Editor," Section: "Server-Side Rendering (SSR)." This section explicitly states, "SSR can reduce initial page load times and improve SEO."

2. Adobe Experience Manager 6.5 Documentation, "Getting Started with SPAs in AEM," Section: "How a SPA Works in AEM." This document explains how the SPA Editor allows for in-context editing of SPA content, fulfilling the WYSIWYG requirement.

3. Adobe Experience Manager Technical White Paper, "AEM with SPAs," Section: "AEM SPA Editor." This resource details the architecture combining the SPA Editor for authoring with Node.js for Server-Side Rendering to meet performance and SEO goals.