Abstract: Concepts and technologies are described herein for managing script file dependencies and load times. In accordance with the concepts and technologies disclosed herein, a server computer stores pages and provides the pages to a client device. The pages can reference and/or rely upon one or more script files during execution and/or rendering. The server computer can determine script file dependencies and load levels associated with the script files. The server computer can generate data such as a directed graph and/or a table that can indicate script file dependencies and script file load levels. The data can be provided to a client device or other entity for use during loading, rendering, and/or execution of the pages.

Abstract: A web application dialog user interface is provided for presenting users with controls for viewing, editing, and otherwise managing content through the web application. Consistency in style and order of control elements in the user interface with control elements of a standard application user interface, launching of the dialog without a page refresh, and maintenance of task continuity provide users a seamless experience in managing their documents through the web application without loss of context.

Abstract: Architecture that enables separation of a user interface (UI) upgrade from the content and application logic upgrade. Administrators can upgrade to take advantage of new infrastructure features, and independently schedule the UI upgrade, for example, to accommodate customization work or to ensure user training. Furthermore, administrators can now allow users to choose when to switch to the new UI. More specifically, the architecture facilitates the separation of a UI upgrade from content and application logic upgrade, the ability to control the UI upgrade at multiple levels of precision, the ability for application logic and UI components to change behaviors based on the UI version of the context, and the ability to “preview” the updated UI before permanently switching to it. Additionally, UI components can be filtered to only appear in the appropriate UI version, and the site's UI version can be compared to versions that a component is compatible with.

Abstract: A cascading stylesheet (CSS) file transformed with user-selected design variables is provided. One or more CSS files may be received as a first input item, and user defined colors, fonts, layout, and images may be received as a second input item. Embodiments provide for determining if the colors and fonts selected by the user are usable and legible. User-selected color and font schemes may be modified if necessary, and a modified CSS file may be outputted to a rendering engine for rendering an aesthetically pleasing, usable, and legible web page.

Abstract: A client computing architecture is provided that utilized minimal download and simulated page navigation features. A client computer may receive a payload comprising delta data in response to a navigation request for an electronic page. The client computer may further parse the delta data for the electronic page, update page contents for the electronic page based on the received delta data, determine whether one or more errors are associated with a page load process for the electronic page, manage a fragment identifier portion of a uniform resource locator (URL) to track a current location in a navigation of the electronic page, and intercept one or more navigation click events to ensure a minimal download strategy navigation.

Abstract: Concepts and technologies are described herein for managing script file dependencies and load times. In accordance with the concepts and technologies disclosed herein, a server computer stores pages and provides the pages to a client device. The pages can reference and/or rely upon one or more script files during execution and/or rendering. The server computer can determine script file dependencies and load levels associated with the script files. The server computer can generate data such as a directed graph and/or a table that can indicate script file dependencies and script file load levels. The data can be provided to a client device or other entity for use during loading, rendering, and/or execution of the pages.

Abstract: A cascading stylesheet (CSS) file transformed with user-selected design variables is provided. One or more CSS files may be received as a first input item, and user defined colors, fonts, layout, and images may be received as a second input item. Embodiments provide for determining if the colors and fonts selected by the user are usable and legible. User-selected color and font schemes may be modified if necessary, and a modified CSS file may be outputted to a rendering engine for rendering an aesthetically pleasing, usable, and legible web page.

Abstract: A theme variation engine generates mock web pages based on selected user inputs defining thematic aspects of a web site. The inputs may include a color, which is used to derive a color palette used in generating the mock web pages. The input can also include an image, which can be transformed in various ways, and a web page layout that determines where the transformed image may be placed. The theme variation engine uses the inputs to generate various mock web pages that the user can select and have the associated thematic parameters saved for future use. Alternatively, certain thematic parameters associated with the selected mock web pages can be used for generating additional mock web pages. The selected thematic parameters can then be used to generate the web site for the user. A computer system may implement execute instructions using a theme variation engine program module.

Abstract: A tab-based collapsible user interface includes selectable user interface tabs, a ribbon area, and an editing surface. When a browse tab is selected, the ribbon area displays information and does not include any user interface controls for performing commands. When the browse tab is selected, a vertical scroll bar is displayed adjacent to the ribbon area and the editing surface. When the vertical scroll bar is used, the ribbon area and the editing surface are both scrolled. When a page tab or a contextual tab is selected, the ribbon area displays user interface controls for performing commands. When a page tab or a contextual tab is selected, a vertical scroll bar is displayed adjacent to the editing surface but not adjacent to the ribbon area. When the vertical scroll bar is used, the contents of the editing surface are scrolled but the ribbon area is not scrolled.

Abstract: Architecture that enables separation of a user interface (UI) upgrade from the content and application logic upgrade. Administrators can upgrade to take advantage of new infrastructure features, and independently schedule the UI upgrade, for example, to accommodate customization work or to ensure user training. Furthermore, administrators can now allow users to choose when to switch to the new UI. More specifically, the architecture facilitates the separation of a UI upgrade from content and application logic upgrade, the ability to control the UI upgrade at multiple levels of precision, the ability for application logic and UI components to change behaviors based on the UI version of the context, and the ability to “preview” the updated UI before permanently switching to it. Additionally, UI components can be filtered to only appear in the appropriate UI version, and the site's UI version can be compared to versions that a component is compatible with.

Abstract: A web application dialog user interface is provided for presenting users with controls for viewing, editing, and otherwise managing content through the web application. Consistency in style and order of control elements in the user interface with control elements of a standard application user interface, launching of the dialog without a page refresh, and maintenance of task continuity provide users a seamless experience in managing their documents through the web application without loss of context.

Abstract: A navigational information display panel is provided for presenting information associated with a location and relationship of a particular web page in context of hierarchical nodes above the web page. The panel may be displayed at a fixed or movable location upon activation of a navigational information control on a browsing application user interface. The panel may include various display structures representing the web page's contextual location in an effective manner along with navigational links for quick navigation to nodes above the web page (and/or at the same level).

Abstract: A tab-based collapsible user interface includes selectable user interface tabs, a ribbon area, and an editing surface. When a browse tab is selected, the ribbon area displays information and does not include any user interface controls for performing commands. When the browse tab is selected, a vertical scroll bar is displayed adjacent to the ribbon area and the editing surface. When the vertical scroll bar is used, the ribbon area and the editing surface are both scrolled. When a page tab or a contextual tab is selected, the ribbon area displays user interface controls for performing commands. When a page tab or a contextual tab is selected, a vertical scroll bar is displayed adjacent to the editing surface but not adjacent to the ribbon area. When the vertical scroll bar is used, the contents of the editing surface are scrolled but the ribbon area is not scrolled.