This document discusses challenges with configuring the DXA digital experience platform and proposes principles and deliverables to address them. It outlines three principles for module configuration: that it should be discoverable, contributable, and manageable. This includes making all modules and their settings visible and searchable, supporting contribution to modules through repositories and definitions, and enabling installation and management of modules across environments. The document proposes deliverables like a module overview GUI, blueprint configuration approaches, module definitions, and support/communication around changes to help achieve these configuration principles.

1. SDL Web
DD4T = DXA
Rise of the Modules
SDL Web MVP Retreat
October 6, 2016

2. 2
Image placeholder
Click on image icon
Browse to image you want
to add to slide
Agenda
○ DXA Challenges
○ Configuration
– Principle 1: All Settings Visible
– Principle 2: Contributable
– Principle 3: Manageable
○ MVP Summit Deliverables

3. 3
Configuration Challenges with DXA
○ In the 5 Stages of Tridion Knowledge*
– What modules are available?
– What can I configure in a module?
○ In implementations
– What’s set up in a specific system?
– I want some parts of DXA, but not all of it
○ In demos
– Is it supported?
– Can I see a demo specific to my industry’s needs?
– I want to manage my own favorite example sites
* https://prezi.com/fmxykjxu16y_/5-stages-of-grief-with-sdltridion-knowledge/
Action Mihai on a serious project

4. 4
Configuration isn’t just about configuring modules.
Configuration is about discoverability, contributions,
and the adoption of modules.

5. 3 principles:
discoverable, contributable,
and manageable

6. 6
Principle 1: Discoverable
“As an implementer, I want to know what I can
configure within a given system quickly.”
This can include:
○ All modules visible from a single screen
○ Settings within 1-2 clicks away
○ Per-Publication settings easily reachable
○ Custom module editors
○ Searchable settings
○ “Automatic” documentation
Example: Chrome settings in 3 tabs
Example: Searchable settings in chrome

7. 7
Principle 2: Contributable
As an implementer or customer, I want to
find, learn about, and contribute to individual
modules easily.
This can include:
Example: SDL AppStore (Language Apps)
Example: Alchemy Webstore
A standard definition Locations to get modules such as
• Name
• Description
• Metadata
• Code repository
• Version number
• Dependencies
• Author(s)
• Etc
• Alchemy Webstore
• NuGet and Maven
• SDL Community
• Partner sites

8. 8
Principle 3: Manageable Modules
“As an implementer I want a way to:
• Install
• Deploy
• Maybe enable/ disable individual
modules”
This should work across DTAP (dev,
test, acceptance, and production) in load
balance scenarios with multiple Content
Delivery environments.
Example: Chrome extensions enabled-status
toggle

9. 9
Deliverables.
Deliverable Volunteers / Voluntold Consider
GUI Extension for module
overview configuration
Tanner, Jonathan, Curlette,
Saurabh
Different approaches to
BluePrinting Configuration
Components (localized vs.
multiple items)
Breakdown Sia and Saurabh • Foundation (which specific
module to DD4T)
• Modules
• Site-specific example
Module Definition Pankaj and David Docs, repository, dependencies,
self-contained, pluggable,
extendible, etc…
Support and Communication
Proposal
Nick and Alvin Which versions and message
around the changes

10. Copyright © 2008-2014 SDL plc. All rights reserved. All company names, brand names, trademarks,
service marks, images and logos are the property of their respective owners.
This presentation and its content are SDL confidential unless otherwise specified, and may not be
copied, used or distributed except as authorised by SDL.
Global Customer Experience Management

11. 11
Foundation, Modules, Example Sites
Foundation
ECommerce
Module 1 Module 2 Module n
Today’s DXA
Module 1 Module 3 Module 4
Foundation