Wednesday, March 27, 2019

Understanding Sitecore SXA: What is SXA?

Previous: What is SXA?

Marketers and technologists often struggle with complex implementations. Faced with a dazzling array of new technologies, organizations everywhere are trying to develop a roadmap that fits the right technologies with their business objectives. But as many have learned, the road to success is often bumpier than expected.

SXA delivers key features out-of-the-box, shifts development away from coding and into UI, and provides a reliable framework for execution.

Projects can now start with a fully-baked scaffolding, that puts mobile first, separates presentation from content, and already contains a host of presentation components. In addition, key features like url management and search are already incorporated, and the execution methodology is clear and well understood.


For Marketers

  • Best practices (“Helix”) baked in
    Consistent structure of content reduces guesswork. Start with a stable solution that is poised to grow as needed.
  • Extensive component suite
    Most of the commonly needed components are ready to go, right out of the box.
  • Search
    No need to invest in a separate search technology for many common search requirements.
  • Multi tenant and siteHost multiple sites in a single infrastructure, with selectively shared content and cross-site link management.
  • Layout and rendering flexibility
    Content editors have more control of layout and appearance. Renderings can be tweaked, extended or created without having to wait for development.
  • Parallel development and content load
    Content pages can be developed in a wireframe mode, and style can be applied is it becomes available.

For Technologists

  • Best practices (“Habitat”) baked inAvoid costly strategic errors in new projects. Coders are immediately familiar with existing projects.
  • Extensive component suiteNo need to develop commonly used components. All pre-built components can be styled, extended or replaced as needed.
  • Search
    Fewer technologies to maintain, fewer integration points to fail.
  • Multi tenant and site
    Less infrastructure to maintain, better re-use of code, and consistent deployment strategy.
  • Layout and rendering flexibility
    Developers focus on new features and capabilities, rather than tweaks to existing artifacts. Fewer regression bugs.
  • Parallel development and content load
    Front end developers can see real-world instances of their design by switching completed pages into their custom theme.