There are other tokens as well:
$compatibleThemes - path to all themese
$theme - currently used theme
$pageDesigns - root of page designs
$partialDesigns - root of partial designs
$currenttemplate - name of the current template
$tenant - path to the current tenant
$site - path to the current site
$home - path to the current site start item (...
There are two ways of doing that:
create your theme using Create new Site dialogue
create your theme manually
1. Create new Site dialogue
Create New Site dialogue lets you create your own theme.
To do it you need to switch to Theme tab and check Create new theme checkbox
After that your site theme will be created somewhere here:
With Sitecore Experience Accelerator you can forget about previous methods, however, there is nothing that will block you from using them.
Before - NO SXA:
you had to decide how your page will look like before you entered content (because the presentation was stored either on SV or somewhere inside different branches)
you couldn't easily switch your ...
Sitecore Experience Accelerator uses a different approach for that.
You can define your access rights for each rendering/group of renderings by changing the access rights to Available Renderings items.
To do it follow these steps
Navigate to Available Renderings node (/sitecore/content/Tenant/Site/Presentation/Available Renderings)
Pick item which ...
You can build a blog on top of SXA
I've created a step by step tutorial how to do it here
Here are default renderings that can be used on blog.
To display posts on homepage you could use Page List or Search Results
If you need comments there are FB comments, Disqus
Screenshots come from XA.Reference site. If you are not sure how to configure them, ...
You should. Here are few things that you should know.
Without this div element your rendering will not be SXA compliant.
If you decide to skip it you will lose following features/abilities:
your rendering will not be able to use "SXA styles". This div is the main wrapper and inside class attribute other classes which can be specified in Rendering ...
After a nice weekend of trial-and-error with the help of DotPeek, here is what I've come up with. This should be a complete example for use after installing the Active Directory module (using version 1.3 with Sitecore 8.2).
With the following code you should now be able to patch domains required when using switchingProviders as well as add domains through ...
This is what I worked out from playing with SxA:
For your controller renderings, you need to make sure your controller inherits from Sitecore.XA.Foundation.Mvc.Controllers.StandardController
Make sure your rendering has a rendering parameters template setup. If you inherit from /sitecore/templates/Foundation/Experience Accelerator/Rendering Variants/...
I love this question because I have an answer. Not long ago I built a module for SXA that would do this. I may not have tested this on your version of SXA, but it should give you an idea how to do it.
Check out this link for more details.
I added a processor called AddPlainIncludes to pull items from the media library and add to the page. SXA comes with a ...
Yes, it's possible. There is a new feature in SXA 1.7.1 which allows you to create an index per site and per language (and of course per database).
On the Site Definition (/sitecore/content/YOUR_TENANT/YOUR_SITE/Settings/Site Grouping/YOUR_SITE) item you will find a new field in the Indexing section:
This field is using a special convention which allows ...
Toolbox displays renderings in a way how they are organised in Renderings content tree.
Available Renderings plays a role of filter only. Those items define which renderings should be added to a toolbox but do not define a way how they are organised.
In your case you've got one of your renderings under Renderings/../News folder and one under Renderings/../...
sitecore/media library/Project/New tenant - this is media folder created for your project. In this example your project is called "New tenant"
sitecore/media library/Project/New tenant/shared media folder an be used when you have more then one site in the tenant. While using it you can share media across all of the pages within that tenant.
To inject something via constructor or get types with Service Locator you need to register your services first.
public class RegisterOoyalaServices : IocProcessor
public override void Process(IocArgs args)
The index.html actually exists in the zip, but is not visible under the standard Windows Expolorer unzipper for some reason. If you use 7Zip to unzip the the package, you should find all files there.
We've addressed the problem and it should be solved in the upcoming release.
It is easy. The implementation steps are low complexity.
See how bootstrap is configured
Create Grid Theme
/sitecore/media library/Feature/Experience Accelerator/Bootstrap/Bootstrap
It is your custom grid theme. The most important thing is to include your css file with all your grid classes
Create Grid Definition
Yes, it is possible to achieve your architecture using Sitecore. There are a few options for you here to do headless implementations, each with their own advantages and disadvantages, and different version/licensing implications.
Currently in Tech Preview, this requires Sitecore 9 and a subscription/consumption license (as mentioned ...
If you want the exact same component - that is not possible. That is probably referring to partial designs - which offer that functionality but those include the full component with its datasource.
If you want to reuse components (or sets of components) and still be able to change the datasource, snippets might be a solution. They can be easily created (...
Yes, you can do it! I will skip part of how the lazy loading should work as this is plenty of blog posts about it like:
But here is one thing SXA SXA can help with. Rendering Variants supports tokens inside of the ...
These items can be queried using code like this:
var siteInfo = ServiceLocator.ServiceProvider.GetService<ISiteInfoResolver>().GetSiteInfo(Context.Item);
if (siteInfo != null)
var siteContext = new SiteContext(siteInfo);
var dictionaryPath = siteContext.Properties["dictionaryPath"];
From numerous experiments, I have put together the following tips and tricks.
Note that a good score under the desktop tab is considerably easier to achieve, the mobile score in our responsive sites is the real score we should benchmark against.
Backend Vs Front End
Page speed can be divided into two distinct parts. Backend server response and front ...
At the moment SXA doesn't support such kinds of mapping. I would recommend to go with Rendering Variants. You can create one rendering variant which will have following fields:
Rendering variants won't render fields which don't exist so Published Date and Profile Picture will be only shown if items of News or ...
This is not a solution I recommend for a production server, but if you need a certificate for a development server, I have a solution for you.
I use use a PowerShell script to create a certificate, and then configure my IIS site to use the certificate.
Here is the script I use. Before running the script you must set the variable $dnsname to the name of ...
You can ignore the errors as long as you make sure you publish the installed items with a Full or Single Item publish.
We have tested this and confirmed this as platform bug in 8.2 (rev 160729), when a package is installed the SaveItem event is not passed a language.
This doesn't effect how Sitecore saves the item data itself, but the ...
Media Library scope for site
Every dialog where you have to select media item will be scoped to Media (Virtual Media Folder)
So first and very important role is to scope which part of Media Library is available for editors on the current site (you will set this up using Additional Children field), see image below
Easy upload/quick access
In fact, this is ...
Yes that is possible.
I created two sites in one sitecore instance. One is SXA based and the other one is on Habitat. These sites are on Sitecore 8.2 update-3 instance with SXA 1.3. As such there wasn't any conflict other than the controller name that should be different from the SXA components for example if you need to build an accordion then the ...
SXA and Feydra are two completely different products attempting to solve completely different requirements. It's like comparing a convenience store (7-11) to a specialty drink store (Smoothie King).
SXA is a product that is in use during the development life-cycle and in production. For example, it includes Creative Exchange to assist developers in ...
Yes, this is possible. There is an easy way to extend/add logic which is missing by implementing custom Variant Token.
This is an example implementation of ResolveParentName processor:
public class ResolveParentName : ResolveVariantTokensProcessor
public override string Token => "$parentName";
public override void ResolveToken(...
My investigation has shown that it can be easily done by configuration. Individual placeholders can be explicitly excluded from wrapping:
<?xml version="1.0" encoding="utf-8" ?>