SDL Digital Experience Accelerator CM-side framework (.NET Template Building Blocks)
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
CoverageReports
Dxa.CM.Extensions
Sdl.Web.DXAResolver
Sdl.Web.DataModel
Sdl.Web.Tridion.Templates.Legacy
Sdl.Web.Tridion.Templates.R2
Sdl.Web.Tridion.Templates.Tests
Sdl.Web.Tridion.Templates
_NuGet
_tools
.gitignore
ClassDiagram1.png
CommonAssemblyInfo.cs
DxaContentManagement.sln
FormatingFeaturesFiltering.xslt
Ionic.Zip.dll
LICENSE
MSBuild.ExtensionPack.dll
MsTest.testsettings
README.md
UploadTemplates.cmd
ciBuild.proj

README.md

dxa-content-management

SDL Digital Experience Accelerator Core Template Building Blocks

About

The SDL Digital Experience Accelerator (DXA) is a reference implementation of SDL Web 8 and SDL Tridion 2013 SP1(*) intended to help you create, design and publish an SDL Web/Tridion-based website quickly.

It is available for .NET and Java Web Applications and has a modular architecture consisting of a Framework and example web application providing core functionality and separate Modules for additional, optional functionality.

This repository contains the source code of the DXA Core Template Building Blocks used on the Content Manager side. The full DXA distribution (including CM-side items and installation support) is downloadable from the SDL Community site or the GitHub Releases of the dxa-web-application-dotnet or dxa-web-application-java repositories.

To facilitate upgrades, it is highly recommended to use an official, compiled version of the DXA Core TBBs (part of the DXA distribution) instead of a custom build. If you really have to modify the DXA Core TBBs, we kindly request you to submit your changes as a Contribution; see below.

Note that the Sdl.Web.Tridion.Templates.csproj project references CM assemblies in _references subdirectories which are not included in this repository, because these assemblies cannot be distributed without a signed license agreement. In order to build the project, the following CM assemblies will have to be obtained from an SDL Web/Tridion distribution and put in the appropriate _references subdirectories:

cm-8.1:

  • Tridion.Common.dll
  • Tridion.ContentManager.Common.dll
  • Tridion.ContentManager.dll
  • Tridion.ContentManager.Publishing.dll
  • Tridion.ContentManager.TemplateTypes.dll
  • Tridion.ContentManager.Templating.dll
  • Tridion.ContentManager.TypeRegistration.dll
  • Tridion.ExternalContentLibrary.dll
  • Tridion.ExternalContentLibrary.V2.dll
  • Tridion.Logging.dll
  • Tridion.TopologyManager.Client.dll
  • Microsoft.OData.Client.dll
  • Microsoft.OData.Core.dll
  • Microsoft.OData.Edm.dll
  • Microsoft.Spatial.dll
  • Newtonsoft.Json.dll

(*) SDL Tridion 2013 SP1 is only supported up to DXA version 1.6.

Support

At SDL we take your investment in Digital Experience very seriously, and will do our best to support you throughout this journey. If you encounter any issues with the Digital Experience Accelerator, please reach out to us via one of the following channels:

Documentation

Documentation can be found online in the SDL documentation portal: http://docs.sdl.com/sdldxa2-ctp

Repositories

The following repositories with source code are available:

Branches and Contributions

We are using the following branching strategy:

  • master - Represents the latest stable version. This may be a pre-release version (tagged as DXA x.y Sprint z). Updated each development Sprint (approx. bi-weekly).
  • develop - Represents the latest development version. Updated very frequently (typically nightly).
  • release/x.y - Represents the x.y Release. If hotfixes are applicable, they will be applied to the appropriate release branch, so that the release branch actually represent the initial release plus hotfixes.

All releases (including pre-releases and hotfix releases) are tagged.

If you wish to submit a Pull Request, it should normally be submitted on the develop branch, so it can be incorporated in the upcoming release.

Fixes for really severe/urgent issues (which qualify as hotfixes) should be submitted as Pull Request on the appropriate release branch.

Please always submit an Issue for the problem and indicate whether you think it qualifies as a hotfix; Pull Requests on release branches will only be accepted after agreement on the severity of the issue. Furthermore, Pull Requests on release branches are expected to be extensively tested by the submitter.

Of course, it's also possible (and appreciated) to report an Issue without associated Pull Requests.

License

Copyright (c) 2014-2017 SDL Group.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.