Abstract: Techniques for providing a cloud mobile device debugging service may be provided. For example, input may be received that is formatted in a particular debugging protocol. The input may be intended for execution on a browser of a mobile device that is remotely hosted with respect to the source of the input. The input may be translated from the particular debugging protocol to a common debugging protocol and provided to the remotely hosted mobile device. A result of executing the translated input with the remotely hosted mobile device may be displayed via a user interface.

Abstract: Techniques for providing a cloud mobile device-debugging server may be provided. For example, a request to initiate a communication channel with a mobile device may be received. The communication channel may be initiated based on the request and status information associated with the mobile device. Further, input may be received for interacting with the mobile device where the input corresponds to a particular input protocol. A proxy for translating and executing the received input may be selected based on the particular input protocol. A result of executing the input on the mobile device may be provided for display.

Abstract: A publishing interface is provided for a user to publish content to a content management server (CMS). The content is authored on a work station by way of an authoring application operating thereon and includes a main body and at least one linked object. Each linked object is linked to the main body by a local pointer therein. The CMS is for effectuating a web site including the published content. The publishing interface has a client-side component working with the application and a server-side component working with the CMS. The client-side component resolves each local pointer to a linked object in the main body, converts the main body into a pre-determined format as determined by the selected task, and forwards the converted main body and each linked object thereof to the server-side component. The server-side component stores the converted main body and the linked objects in the CMS.

Abstract: A publishing interface is provided for a user to publish content to a content management server (CMS). The content is authored on a work station by way of an authoring application operating thereon and includes a main body and at least one linked object. Each linked object is linked to the main body by a local pointer therein. The CMS is for effectuating a web site including the published content. The publishing interface has a client-side component working with the application and a server-side component working with the CMS. The client-side component resolves each local pointer to a linked object in the main body, converts the main body into a pre-determined format as determined by the selected task, and forwards the converted main body and each linked object thereof to the server-side component. The server-side component stores the converted main body and the linked objects in the CMS.