Sitecore-10-NET-Developer Exam Dumps : Sitecore 10 .NET Developer Exam

The field helper is a Sitecore MVC helper that renders the content of a field in the view. It also enables the field to be editable in the Experience Editor or Horizon. To prevent a field from being edited, you can set the editable parameter to “false” in the field helper. For example, @Html.Sitecore().Field(“title”, new { editable = false }) will render the title field without the editing capabilities. This parameter overrides the default behavior of the field helper, which is to render the field as editable if the page is in edit mode. Setting the editable parameter to “false” can be useful for fields that are not meant to be changed by the content authors, such as system fields or fields that are populated by code. 

 Sitecore headless development is based on a decoupled architecture where the rendering host is a separate application that handles the presentation logic and the Content Delivery role is a Sitecore instance that handles the content management and delivery. The rendering host communicates with the Content Delivery role using Sitecore headless services, which are APIs that expose Sitecore content and layout data in a JSON format. The rendering host translates a visitor request to a content item in the Sitecore instance. The Sitecore instance using Sitecore headless services returns the content item and the associated presentation details, and so on, to the rendering host. The rendering host renders the content item for the visitor. This way, the rendering host can use any technology or framework that supports HTTP requests and JSON parsing, such as ASP.NET Core, React, Angular, Vue, etc. References:

• Headless development with the ASP.NET Rendering SDK
• Sitecore Headless Development FAQ
• Sitecore Headless Development

Field editor buttons are custom experience editor buttons that allow content authors to edit multiple fields of an item in a pop-up window. This is useful for complex fields that are not easily editable in the experience editor, such as multilist fields, checkbox fields, or image fields. Field editor buttons can also be configured to edit the fields of the data source item of a rendering, rather than the page item. Field editor buttons can improve the content authoring experience by providing a convenient and consistent way to edit fields in the experience editor. References:

• 12
• 13
• 14