Recommendations: Example SXA project workflow

Current version: 10.1

SXA is a flexible tool and there are several different ways to run an SXA project workflow. All workflows have their own benefits and greatly depend on the skill set of the team. The following infographic describes a workflow for SXA projects that we have found to be successful and efficient for an implementation at a full-service agency:


Start every SXA project by determining how you are going to use SXA:

  • Define the goal of the website(s).

  • Define the KPIs to measure success.

Think about the content and styling of your site(s):

  • Is there a need to share content and presentation? Consider using Shared site as the exclusive style container in a tenant. It is good practice to have a shared site within every tenant. Read the recommendations on sharing content here.

  • Do you want a multilingual implementation?


Inform your UX and design team about SXA, its default renderings, and its ability to define rendering variants at the beginning of the design process. Encourage them to use out-of-the-box components. It is important to understand the functionality and aim of each component. Explain the possibility to clone components and to create custom components for more complex solutions. Use the flowchart to help decide whether you need to create a custom component.


Perform a gap analysis between your completed design and SXA’s out-of-the-box toolset. Map the designs with OOTB components to see which components can be used and which ones require custom development.

Let your SXA expert architect the site’s page layouts and components, putting together example pages for content editors and developers to work with.


After your SXA expert defines first-draft examples of layouts and renderings, and a MVP is available, each of the following tasks can happen in parallel:

Do you have some feedback for us?

If you have suggestions for improving this article,