Abstract: Provided are techniques for mode-specific search query processing. A current search query is received from a user, wherein the user has a user profile. In response to determining that a query mode for the current search query is a guided mode, a query context of the current search query is determined. A classification for the current search query is determined. One or more search influencers are identified using the classification, where each of the one or more search influencers has a corresponding user profile. The current search query is rewritten based on the query context, a private portion of the user profile of the user, and a public portion of each corresponding user profile of each of the one or more search influencers. The rewritten search query is executed to generate search results, and the search results are returned.

Abstract: Provided are techniques for mode-specific search query processing. A current search query is received from a user, wherein the user has a user profile. In response to determining that a query mode for the current search query is a guided mode, a query context of the current search query is determined. A classification for the current search query is determined. One or more search influencers are identified using the classification, where each of the one or more search influencers has a corresponding user profile. The current search query is rewritten based on the query context, a private portion of the user profile of the user, and a public portion of each corresponding user profile of each of the one or more search influencers. The rewritten search query is executed to generate search results, and the search results are returned.

Abstract: A computer-implemented method for enabling static markup crawlability for a web application dynamically updating web pages client-side may be provided. The method comprises providing a web application identifiable by a web address comprising both, a static content block and dynamic content, and generating a static HTML page and pre-rendering the static content block of the web application such that at least a portion of static content of the web application is crawlable.

Abstract: Provided are techniques for mode-specific search query processing. A current search query is received from a user, wherein the user has a user profile. In response to determining that a query mode for the current search query is a guided mode, a query context of the current search query is determined. A classification for the current search query is determined. One or more search influencers are identified using the classification, where each of the one or more search influencers has a corresponding user profile. The current search query is rewritten based on the query context, a private portion of the user profile of the user, and a public portion of each corresponding user profile of each of the one or more search influencers. The rewritten search query is executed to generate search results, and the search results are returned.

Abstract: Automatically generating a client-side application based on available components is provided. A source code and related build information of a component is stored in a component repository. The component is developed in a developer mode of a developer tool. An existing single-page application is changed using a non-expert editing tool by selecting a component from the component repository, retrieving the selected component from the repository, extracting build information from the retrieved component, adding dependencies regarding the retrieved component to a single-page packaging of the existing single-page application, and compiling the single-page application together with the retrieved component.

Abstract: A computer-implemented method for improving cachability of an API request result of a content delivery system may be provided. The method comprises maintaining a unique seed value per group of content items of a content type, and, upon determining that one of the content items of the group is updated, updating the seed value for the group of content items. The method also comprises caching one of the content items of the group together with the related seed value in a caching system and receiving, by the caching system, an API request requesting as API request result a content item of the group, wherein a parameter of the API request is a selected seed value.

Abstract: A computer-implemented method for enabling static markup crawlability for a web application dynamically updating web pages client-side may be provided. The method comprises providing a web application identifiable by a web address comprising both, a static content block and dynamic content, and generating a static HTML page and pre-rendering the static content block of the web application such that at least a portion of static content of the web application is crawlable.

Abstract: Automatically generating a client-side application based on available components is provided. A source code and related build information of a component is stored in a component repository. The component is developed in a developer mode of a developer tool. An existing single-page application is changed using a non-expert editing tool by selecting a component from the component repository, retrieving the selected component from the repository, extracting build information from the retrieved component, adding dependencies regarding the retrieved component to a single-page packaging of the existing single-page application, and compiling the single-page application together with the retrieved component.

Abstract: A method, system, and/or computer program product provides client-side aggregation of web content. A client system receives a first and second set of content to be displayed on a web page and an associated style sheet describing a visual layout to be used when displaying the web page. The first and second sets of content are aggregated to create a combined set of content. A fully aggregated web page is created by transforming the combined set of content into a hypertext markup language (HTML) document. A browser on the client system then renders and displays the fully aggregated web page. An activation of an element on the rendered fully aggregated web page is detected, causing a change to the combined set of content. In response to detecting the activation of the element, a full page refresh of the rendered fully aggregated web page is executed.

Abstract: A method, system, and/or computer program product provides client-side aggregation of web content. A client system receives a first and second set of content to be displayed on a web page and an associated style sheet describing a visual layout to be used when displaying the web page. The first and second sets of content are aggregated to create a combined set of content. A fully aggregated web page is created by transforming the combined set of content into a hypertext markup language (HTML) document. A browser on the client system then renders and displays the fully aggregated web page. An activation of an element on the rendered fully aggregated web page is detected, causing a change to the combined set of content. In response to detecting the activation of the element, a full page refresh of the rendered fully aggregated web page is executed.

Abstract: A method, system, and/or computer program product provides client-side aggregation of web content. A client system receives a web content structure document of a web page with an associated style-sheet. The web content is aggregated on the client-side by transforming the web content structure document into a target web page document by using the style-sheet, wherein during the aggregation further web content is received based on information in the web content structure document using the style-sheet document resulting in a fully aggregated web page, and wherein the aggregation does not interfere with any other client-side transformation of the web content. The fully aggregated web page is then rendered and displayed.

Abstract: Deploying portlet(s) onto a displayed portal page by dragging and dropping portlet related artifacts from the IDE like portlet deployment descriptor node or a specific portlet node, and, responsively displaying the portlet(s), corresponding to the dropped node, in the displayed portal page. The updating of the portal page is accomplished by an internal IDE browser of a stand-alone type IDE working co-operatively with a remote portal server.

Abstract: Deploying portlet(s) onto a displayed portal page by dragging and dropping portlet related artifacts from the IDE like portlet deployment descriptor node or a specific portlet node, and, responsively displaying the portlet(s), corresponding to the dropped node, in the displayed portal page. The updating of the portal page is accomplished by an internal IDE browser of a stand-alone type IDE working co-operatively with a remote portal server.

Abstract: Deploying portlet(s) onto a displayed portal page by dragging and dropping portlet related artifacts from the IDE like portlet deployment descriptor node or a specific portlet node, and, responsively displaying the portlet(s), corresponding to the dropped node, in the displayed portal page. The updating of the portal page is accomplished by an internal IDE browser of a stand-alone type IDE working co-operatively with a remote portal server.

Abstract: Deploying portlet(s) onto a displayed portal page by dragging and dropping portlet related artifacts from the IDE like portlet deployment descriptor node or a specific portlet node, and, responsively displaying the portlet(s), corresponding to the dropped node, in the displayed portal page. The updating of the portal page is accomplished by an internal IDE browser of a stand-alone type IDE working co-operatively with a remote portal server.

Abstract: Deploying portlet(s) onto a displayed portal page by dragging and dropping portlet related artifacts from the IDE like portlet deployment descriptor node or a specific portlet node, and, responsively displaying the portlet(s), corresponding to the dropped node, in the displayed portal page. The updating of the portal page is accomplished by an internal IDE browser of a stand-alone type IDE working co-operatively with a remote portal server.

Abstract: Deploying portlet(s) onto a displayed portal page by dragging and dropping portlet related artifacts from the IDE like portlet deployment descriptor node or a specific portlet node, and, responsively displaying the portlet(s), corresponding to the dropped node, in the displayed portal page. The updating of the portal page is accomplished by an internal IDE browser of a stand-alone type IDE working co-operatively with a remote portal server.

Abstract: Embodiments of the present invention provide systems, methods, and computer program products for modifying a published portlet. According to one embodiment, a server computer system renders a published portlet to a thin client interface of a client computer system. The server computer system receives a request for a design page of the portlet, renders the design page on the thin client interface, and receives modifications to the content of the portlet using the design page. Modified content of the portlet is stored as a portlet resource.

Abstract: Embodiments of the present invention provide systems, methods, and computer program products for modifying a published portlet. According to one embodiment, a server computer system renders a published portlet to a thin client interface of a client computer system. The server computer system receives a request for a design page of the portlet, renders the design page on the thin client interface, and receives modifications to the content of the portlet using the design page. Modified content of the portlet is stored as a portlet resource.

Abstract: Deploying portlet(s) onto a displayed portal page by dragging and dropping portlet related artifacts from the IDE like portlet deployment descriptor node or a specific portlet node, and, responsively displaying the portlet(s), corresponding to the dropped node, in the displayed portal page. The updating of the portal page is accomplished by an internal IDE browser of a stand-alone type IDE working co-operatively with a remote portal server.