5
The Page Design that you're seeing isn't processed by the React application, it's just part of the default Item serialization.
The power of SXA's Page + Partial Designs will translate into a list of placeholders, components, and nested placeholders in the JSON, no different than a non-SXA site.
You need to start off with ensuring your JSS Layout definition ...
3
There are few options:
Use Sitecore RESTful API. It doesn't matter SXA or not, but you will be able to get items in JSON format.
Use JSON device to get page data. SXA allows you to model your data in JSON. You are able to use special JSON renderings to model data in a way that you need. But even if your website uses default renderings, you can use the SXA ...
3
If local or page relative SXA data sources are not resolved you need to resolve them manually. Run resolveRenderingDatasource pipeline:
ResolveRenderingDatasourceArgs renderingDatasourceArgs = new ResolveRenderingDatasourceArgs(YOUR_DATA_ROURCE_STRING);
renderingDatasourceArgs.CustomData.Add("contextItem", CONTEXT_ITEM);
CorePipeline.Run("...
3
As Mark mentioned in his comment you should use the SXA tokens to achieve this. You can find a list here: https://doc.sitecore.com/en/developers/sxa/101/sitecore-experience-accelerator/the-sxa-pipelines.html
Useful ones for sources in templates could be:
$tenant - path to the current tenant.
$site - path to the current site.
$home - path to the current site ...
1
SXA has a custom pipeline called normalizeSearchPhrase which is removing all special characters from the search phrase. All the characters from this HashSet are removed:
new HashSet<string> { "-", "+", "&", "|", "!", "{", "}", "[", "]", "^", "(&...
1
In my case, the base template in the Site Node template was missing the _Modules template
/sitecore/templates/Foundation/Experience Accelerator/Scaffolding/_Modules
So, after adding this, the script error has been resolved.
1
It looks like it could not be done with SXA CLI out of the box.
But, it is possible to do with modification of SXA gulp scripts.
Option 1:
Quick and dirty.
It is possible to save CSS source map in the same .css file.
(it doesn't work for production, but for all other environments it should be OK)
Open \node_modules\@sxa\celt\util\cssMinificator.js
Change ...
Only top voted, non community-wiki answers of a minimum length are eligible
