Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
DXA Web Application Overview
Transcript of DXA Web Application Overview
DXA Web Application Overview
No rendering in Tridion Templates
All content + binaries -> Broker DB
Content published in data format (DD4T)
URL request ->
Controller uses Content Provider to load content from broker DB into a
Controller passes Model to a
Mobile Friendly using RESS
Built with extension in mind
Decoupled from CD Architecture
Hide CMS Peculiarities
Experience Manager "Ready"
Views == Page Layout (relation is managed in PT meta)
Views == Component Layout (CT meta)
Views allow us to render content in different areas, do column layouts (Region defined in CT meta)
(demo page composition)
View Models: Optimized models rendered by Views:
from CMS Model (schema)
: only contain properties required
to make sense to View Developers
DXA hides Tridion behind a
which loads and transforms content to build the models to be rendered by views
is currently only option
Could even be a different storage (
?) or CMS!
Other than flexibility, the main reason to do this is to reduce CMS understanding required for web developers
: Remove need to understand XPM markup when creating views, and keep views
Self-contained packages of web application functionality: Views, Controllers, Models, Integration code
Goal is to make easier to
Typically packaged into a
DLL + View files
Usually also have
(schemas, templates, config etc.)
defines the Module where Controller and/or Views are located
(demo Modules/Areas in project
Developers markup Entities and properties
Can also be used to support Semantic Web -
(demo - View/Model code and rendered content)
View Models - example
With strongly typed view model:
With a CMS type Model:
How does it work?
View Models are created based on content to be rendered
Annotations indicate relation to CMS Model
A generic Model Builder populates the View model from the CMS Model (Component Presentation) "behind the scenes"
Sensible defaults mapping schema fields:
(multival embedded) ->
Links and RTF are resolved in the proces using a
Properties can be
Multiple fields -> single property
Multiple schemas -> single Entity
Single schema -> multiple Entities
(demo complex model annotation: Teaser)
More detail in online docs ("Semantic Mapping")