Coveo .NET Front-End Interface Editor
Example: You can create a search interface to integrate in a Web page and another to integrate in a SharePoint intranet. Each of these search interfaces can have different scopes, options, CSS formats, etc.
The .NET Interface Editor user interface is organized in tabs:
Search Hubs tab
Used to set the hub name, available search interfaces for the standard, mobile and Outlook versions of a hub. Set the width, position, default culture and facet position of search interfaces (see .NET Interface Editor - Search Hubs Tab).
Search Interfaces tab
Used to configure all aspects of each search interface: available features, CSS styles, facets, preference defaults, and more (see .NET Interface Editor - Search Interfaces Tab).
Used to define groups of users that can be assigned to control access to search interfaces (see What Is an Audience?).
Used to set custom file types, per URI settings, and languages (see .NET Interface Editor - Miscellaneous Tab).
Used to replicate search hub and search interface configurations to other Front-End servers (see .NET Interface Editor - Deployment Tab).
The .NET Interface Editor keeps the configuration data in an XML file stored on the Front-End server. In a Coveo topology with multiple Front-End servers, the best practice is to use on of the Front-End servers as the source on from which you deploy the configuration to the other servers (see Deploying Search Interface Settings).
Note: You can also transfer search interface configuration files from one Coveo instance to another. This process is useful for example when you want to transfer changes to a search interface between the Coveo instances in your development, quality assurance, and production environments.