Abstract: A system is provided and includes search, analytics acquisition, CTR, and scoring modules. The search module: receives query requests from one or more user devices for respective queries; and based on the query requests and a CTR-based scoring model, conducts searches to provide search results for the queries. The analytics acquisition module acquires analytics data corresponding to the queries. The analytics data includes query files for the queries and selection files for the queries for which a selection event occurred. At least some of the selection events occur when a user of the one or more user devices selects a search result item in the search results provided for the queries. The CTR module determines a normalized CTR based on the analytics data. The scoring module updates the CTR-based scoring model based on the normalized CTR. The search module conducts a search based on the updated CTR-based scoring model.

Abstract: Icons for use and display in a graphical user interface (GUI) on a client are generated on a server. The icons (e.g. bitmaps, PNG, GIF, JPEG . . . ) that may be used in the GUI are created by the server and reflect a theme that is associated with a document. The icons used in the GUI may contain advanced graphical effects (e.g. shadows, gradients, reflections, glows, 3D perspectives, and the like) that may not be able to be generated by the client. The icons may be rendered automatically (e.g. during initial processing of a theme for a document, in response to an action) and/or upon demand. The icons are grouped by the server and information about the individual icons is saved as metadata. The client receives the grouped icons and corresponding metadata and accesses the icons to create a display of GUI elements such as galleries, buttons, and dialogs.

Abstract: Presentation content is embedded within a Web page utilizing a presentation Web Part. The presentation Web Part is configured to create a Web element, such as an inline frame (“iFrame”) within which the presentation content can be displayed. The presentation Web Part is configured with an outer application programming interface (“API”) that functions as a message wrapper, such as a postMessage wrapper, for an inner API to call functions of a presentation Web application to manipulate the presentation content such as by advancing through various slides of the presentation content. For example, the presentation Web Part and a map Web Part may be displayed on the same Web page such that when a user selects a city or other location via the map Web Part, the presentation Web Part displays presentation content associated with the selected location. Other use cases are provided herein.