SCS is pretty new, and there are a few basic recommendations while doing the first setup, In this blog, we will discuss those settings and options.
This blog has split into three parts, and this is part 3.
In Microsoft NTFS the maximum length is 240. In SCS the content serialization path size limit is defined in the settings, by default, the value is 100.
The maximum relative item path length = the file system maximum path and file name length – (the base path length + the serialization path length). for more details, please follow this link – Configure the maximum relative item path length
Hashing to shorten paths and aliases and to make it human readable.
It’s super important for two purposes. One is to mitigate the risk of serialization path, and second is define the structure of the project like we can define common aliases for the site.
Relative path is combination of four section (Base path + serialization path +include path content item path).
define the alias
As a rule of thumb with Sitecore, all the dependencies should be defined first, for example before defining the content we have to define the templates, layout and rendering etc.
...while defining the IA or base principle of the content sync strategy – this rule says when a content item matches a rule, all subsequent rules are ignored:
As per the Sitecore recommendation, we need Keep the following things in mind when we configure rules:
For more details, please follow below links:
I hope this blog will help you to think of a few fundamental considerations while starting to work with SCS on Sitecore.