Abstract: Techniques are described for resolving document change conflicts based on state information. A document management system records, at a client device, changes that a user made to a root client-side instance of a document bundle to create a modified client-side instance of the document bundle, wherein the changes were made while the client device was not connected to a remote storage service. After the changes are recorded, the client device is connected to the remote storage service. In response to determining that a conflict has occurred, the document management system selects a particular resolution action, based, at least in part, on state information associated with at least one of: a user that made the changes, an instance of the document bundle, or the client device on which the changes were made. The document management system then resolves the conflict by performing the particular resolution action.

Abstract: A method includes analyzing a first document to identify a first set of one or more tags and responsive to identifying the first set of one or more tags: automatically producing a second document based in part on first set of one or more tags, where the second document includes one or more accessibility features that were not in the first document.

Abstract: Techniques are described for display and navigation of hierarchical messages, which displays include contextual data for the messages. Context information for a current message includes reply messages, parent messages, and metadata representations. Message representations are also associated with visual depth indicators that are independent of the text of the messages. Users may navigate displays of hierarchical message data using different navigational inputs. For example, more information may be requested for messages, without selecting a new message for viewing as a focal message, using swipes across portions of the display dedicated to displaying the messages. A limited number of messages for a requested list of messages is initially retrieved and displayed, and a mechanism for viewing more messages from the list is provided. Historical usage of the mechanism is recorded and the number of messages to be displayed for the list of messages is adjusted based on the historical usage data.

Abstract: An improved system and method for providing software is described. The system, upon receiving a software request from a user device, obtains metadata about the user device. Based on the metadata and the software requested, a template of the software is obtained. The template specifies a list of categories, where each category is associated with component(s) in a component database. Based on the metadata and eligibility attributes of the respective components, one component from each category is selected for inclusion in the software. From the selected components and the template, the requested software is constructed and sent to the user device. In some embodiments, for popular user devices, a previously stored selection of components can be accessed. In some embodiments, an updated version of the software is provided if the metadata of the user device changes or if there is a change in the available components or software templates.

Abstract: Techniques for teaching geometric proof problems are described. According to one approach, the geometric proof application displays a geometric proof problem and a set of connectable nodes in an initial arrangement. A user then rearranges the set of connectable nodes and connects them using one-way connections to generate a solution. The geometric proof problem is solved if the user-generated solution indicates the correct logical ordering of the set of connectable nodes as determined by the geometric proof application.

Abstract: A mechanism is provided for controlling a process on a computing node. In one implementation, a determination is made as to whether the participation status of a computing node has changed. The participation status may, for example, be active, in which case the computing node is participating in the processing of requests from a request handler, or it may be passive, in which case the computing node is not participating in the processing of requests from the request handler. In response to a determination that the participation status of the computing node has changed from a current status to a new status, one or more processes on the computing node may be caused to begin or halt processing, in accordance with the new status. For example, if the current status is passive and the new status is active, a process on the computing node may be caused to begin processing.

Abstract: An automated resource resolver system receives a client request for a learning resource. The system selects a format for a target resource, to be delivered to the client device, based on user information and context information for the client device. Thus, the selected format will be accessible by the client device, utilizing the capabilities of the device, and will be the best-fit format for the user. After the system selects the format, the system determines whether the target resource stored at a resource repository is in the selected format. If not, then the system selects an instance of the target resource, not in the selected format, to convert to the selected format. The system converts the selected resource instance to produce an instance of the target resource that is in the selected format. The system makes the target learning resource, in the selected format, available to the client device.

Abstract: Techniques are described for displaying help articles, for a web page, that are related to the context of the web page. A help article provider has access to a database of help articles, each of which are associated with target-context data that may include content identifiers for the help article and/or user profile attributes for users that the help article targets. The help article provider identifies content identifiers for a viewed web page based on one or more of: metadata and a URL for the web page. The help article provider searches the help article database using the identified content identifiers. The help article provider may filter the help articles based on an authenticated user's attributes. An ordered list of the identified help articles is displayed, with the most relevant or important help articles displayed at or near the top of the list.

Abstract: Techniques are described for display and navigation of hierarchical messages, which displays include contextual data for the messages. Context information for a current message includes reply messages, parent messages, and metadata representations. Message representations are also associated with visual depth indicators that are independent of the text of the messages. Users may navigate displays of hierarchical message data using different navigational inputs. For example, more information may be requested for messages, without selecting a new message for viewing as a focal message, using swipes across portions of the display dedicated to displaying the messages. A limited number of messages for a requested list of messages is initially retrieved and displayed, and a mechanism for viewing more messages from the list is provided. Historical usage of the mechanism is recorded and the number of messages to be displayed for the list of messages is adjusted based on the historical usage data.

Abstract: A user interface architectural pattern for product/platform user experience is described. In an embodiment, a request associated with a first macro file is made. The first macro file refers to a second macro file, and includes one or more elements embedded in a wrapper associated with the second macro file. Based at least in part on the second macro file, a user interface component is generated.

Abstract: A reliable caching mechanism is provided for client-side caching of data that captures user interaction with a remote service, where users interact with the remote service through a computing device. Such instrumentation items are cached in a client-side offline queue. Within the client-side queue, the gathered instrumentation items survive between user sessions with the remote service. Because the client-side does not lose the instrumentation items that were gathered in a session when the session ends, those instrumentation items do not all need to be transferred to the server-side at or prior to the termination of the session in which the instrumentation items are collected. Instead, the instrumentation items may be sent to the server-side at times that will have less impact on the user experience, such as when the computing device is otherwise idle.

Abstract: Techniques are described for display and navigation of hierarchical messages, which displays include contextual data for the messages. Context information for a current message includes reply messages, parent messages, and metadata representations. Message representations are also associated with visual depth indicators that are independent of the text of the messages. Users may navigate displays of hierarchical message data using different navigational inputs. For example, more information may be requested for messages, without selecting a new message for viewing as a focal message, using swipes across portions of the display dedicated to displaying the messages. A limited number of messages for a requested list of messages is initially retrieved and displayed, and a mechanism for viewing more messages from the list is provided. Historical usage of the mechanism is recorded and the number of messages to be displayed for the list of messages is adjusted based on the historical usage data.

Abstract: Techniques are provided for navigating through a hierarchy of views while generating a bread-crumb display that continues to provide an indication of each ancestor view even when the labels for all ancestor views do not fit within the bread-crumb display. When the bread-crumb display does not have sufficient room remaining to accommodate the label of a view to which the user has navigated, the current content of the bread-crumb display contracts, like an accordion, to make room for the new label. The contracted version of the bread-crumb display continues to have an indication of all traversed levels, though the labels for some or all of the ancestor views may be partially or completely obscured. The contracted version of the bread-crumb display may be expanded, and used to navigate back up the hierarchy.