3

In vanilla JavaScript, the convention is to use camelCase for field names, and PascalCase for class names. In React, the convention is to use PascalCase only for component names. So to answer your question, I'd recommend camelCase for the actual field names, and utilizing display names for the Content Author's readability sake.


3

Your understanding is not correct. It is indeed the Title field which is displayed above the Field in the Content Editor. By default, this is set to the Field’s name, but you may change the value if you wish. If you want to display even more information, you can use the Help section (Long Description and Short Description) as explained in this Q/A: How to ...


2

We also encountered this issue and solved it by creating an extra layer of templates - might not be the best solution but it works. So what we did: create an extra template on top of the one you normally create as developer keep these templates in a separate folder (structure) for convenience pages are create based on these templates these templates cannot ...


2

Finally figured this out! Most of the links I was trying to apply this validator to were of type General Link with Search. For a field type validator to run, evidently you need to have a Field Type Validation Rules template in the Field Types folder that exactly matches the name of the field you're trying to validate. The path to this field types folder is ...


2

No, this is not possible that two items based on the same template will not have the same fields. If you need this kind of items then you need to create two separate templates that can use a single base template with the common fields and specific fields on the template itself.


1

Why would you use standard values on SXA page templates? You should use page designs... It is logical that the variants are not found as your template does not live in a site (and your page does) and variants are defined per site. But as mentioned, use page designs: https://doc.sitecore.com/developers/sxa/93/sitecore-experience-accelerator/en/page-designs....


1

Let's say you start with a template like the following: Then the following script will move items to a newly created section like this: Using this sample, you can build in whatever logic you want. Keep in mind that if you are wanting to move fields between templates then you need to change the inheritance first. # Get the template I want to change $...


1

I can at least answer part two of your question, as I had to update that myself. At least on v9.3, the source query for the "Allowed in templates" field is query:$templates|$rvSystemTemplates Specifically, $rvSystemTemplates is driven by configuration. You can add the following config file to get your templates to show up in the list <...


1

You may not able to achieve this in a multilist with out-of-box features. The query for your requirement should be like this query:/sitecore/content/FAQ/*[contains(@FAQCategory, 'Current-FAQ-Category-ID')] but unfortunately you can't build like this in source field of a multilist, because there is no way to pass your "Current FAQ Category ID" in the ...


Only top voted, non community-wiki answers of a minimum length are eligible