Abstract: A container document can include a file node indicating a file and pointing to a location for the file that is separate from the container document on a server. An embedded relationship between the file and the container document can be imitated. The imitation can include responding to user input by performing the update on the file node, and by requesting that the server perform an update on the file that reflects the update performed on the file node. A request for an update to be performed on the file node can be received from a client at the server. In response to the request, the update can be performed on the file node at the server. A corresponding update, which reflects the update performed on the file node, can also be performed on the file at the server.

Abstract: A container document can include a file node indicating a file and pointing to a location for the file that is separate from the container document on a server. An embedded relationship between the file and the container document can be imitated. The imitation can include responding to user input by performing the update on the file node, and by requesting that the server perform an update on the file that reflects the update performed on the file node. A request for an update to be performed on the file node can be received from a client at the server. In response to the request, the update can be performed on the file node at the server. A corresponding update, which reflects the update performed on the file node, can also be performed on the file at the server.

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 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 request for a page in a site can be received. The page can include a dynamic navigation region. The dynamic navigation region can be automatically updated based on usage of the site by multiple user profiles. The updating can include querying multiple sources of navigation item data and compiling a record of dynamic navigation items to be displayed in the dynamic navigation region. The page can be generated with the dynamic navigation region, and the page can be returned in response to the page request. Also, a request to pin a navigation item from the dynamic navigation region to the static navigation region can be received. In response to the request to pin, the pinned navigation item can be added to the static navigation region, and the page can be returned with the pinned navigation item added to the static navigation region.

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 method is presented for editing and saving a web page at a client based web-page editor. A rendered web page is received from a server computer and displayed at a web-page editor on the client computer. The client computer identifies one or more customizable web parts on the web page and also identifies one or more shared templates that are associated with the customizable web parts. Each identified shared template is copied as an overriding template. A data view of one or more web parts is edited, causing one or more of the overriding templates associated with the web part to be modified. When the edited changes are saved, the client computer sends a message to the server computer. The message includes the portions of the overriding templates that are modified as a result of the edited changes to the web page.

Abstract: A method is presented for editing and saving a web page at a client based web-page editor. A rendered web page is received from a server computer and displayed at a web-page editor on the client computer. The client computer identifies one or more customizable web parts on the web page and also identifies one or more shared templates that are associated with the customizable web parts. Each identified shared template is copied as an overriding template. A data view of one or more web parts is edited, causing one or more of the overriding templates associated with the web part to be modified. When the edited changes are saved, the client computer sends a message to the server computer. The message includes the portions of the overriding templates that are modified as a result of the edited changes to the web page.

Abstract: Technologies are described herein for declaratively defining forms and views and for rendering the declaratively defined forms and views. A declarative and rendering technology agnostic form definition is defined and stored that defines a layout for a form. A transformation definition file is also stored that defines a transformation from the declarative form definition to renderer-specific code. A transformation is performed using the transformation definition file, the declarative form definition, and form data provided by an application to generate renderer-specific markup for the form. The desired form will be displayed when a rendering client is utilized to render the renderer-specific markup. A view may also be declaratively defined, transformed, and rendered similarly.

Abstract: Instead of using a single template to define a view, multiple interchangeable templates are selected to create a view. The interchangeable templates are shareable across different views which helps in creating different views without requiring users to hard code the changes to the view within a single template. The selected interchangeable templates defining the view are accessed and used to render the display of the view.