Abstract: A content management system (CMS) for managing content types across multiple content spaces is provided, said CMS being configured to perform the following operations: receiving, through a template creation interface, a selection of content types of a source content space; generating a template having said selection of content types, and storing said template to a template library; receiving a command to install the template into a destination content space; responsive to said command, installing the content types of the template into the destination content space, and establishing a link between the destination content space and the template such that the installed content types are identified as being managed via the template.

Abstract: In a content management system (CMS), a method for managing content types across multiple content spaces is provided, including: receiving, through a template creation interface, a selection of content types of a source content space; generating a template having said selection of content types, and storing said template to a template library; receiving a command to install the template into a destination content space; responsive to said command, installing the content types of the template into the destination content space, and establishing a link between the destination content space and the template such that the installed content types are identified as being managed via the template.

Abstract: A non-transitory computer readable medium having program instructions configured, when executed by at least one server computer, to cause said at least one server computer to perform a method implemented in a content management system (CMS) for managing content types across multiple content spaces, said method including the following method operations: receiving, through a template creation interface, a selection of content types of a source content space; generating a template having said selection of content types, and storing said template to a template library; receiving a command to install the template into a destination content space; responsive to said command, installing the content types of the template into the destination content space, and establishing a link between the destination content space and the template such that the installed content types are identified as being managed via the template.

Abstract: A process for rendering a user interface for launching content for publication using a content management system (CMS), includes: providing, over a network, an editor application enabling editing of entities stored in the CMS; providing, over the network, a launch application, wherein execution of the launch application renders the user interface for launching content for publication, wherein the user interface includes a reference tree providing a hierarchical visualization of reference relationships amongst the entities; receiving selection of a group of entities for publishing; and generating, responsive to the selection, an application programming interface (API) call to the CMS to trigger initiation of a validation process to validate each entity, without requiring separate API calls for validating each entity; and, wherein the validation process, once initiated, proceeds automatically without requiring said separate API calls to separately initiate publication of each of the entities in the group of ent

Abstract: A process for rendering a user interface for launching content for publication using a content management system (CMS), includes: providing, over a network, an editor application enabling editing of entities stored in the CMS; providing, over the network, a launch application, wherein execution of the launch application renders the user interface for launching content for publication, wherein the user interface includes a reference tree providing a hierarchical visualization of reference relationships amongst the entities; receiving selection of a group of entities for publishing; and generating, responsive to the selection, an application programming interface (API) call to the CMS to trigger initiation of a validation process to validate each entity, without requiring separate API calls for validating each entity; and, wherein the validation process, once initiated, proceeds automatically without requiring said separate API calls to separately initiate publication of each of the entities in the group of ent

Abstract: A process for rendering a user interface for launching content for publication using a content management system (CMS), includes: providing, over a network, an editor application associated with the CMS, enabling editing of entities stored in the CMS, the editing includes authoring fields for each entity; providing, over the network, a launch application, wherein execution of the launch application renders the user interface for launching content for publication; receiving selection of a group of entities, via the user interface, the selection is for publishing the group of entities; and generating, responsive to the selection, an API call to the CMS, that triggers initiation of a validation process to validate each entity in the group of entities, wherein the validation process is executed in a draft entity store of the CMS that is created for said validation without requiring separate API calls for validating each entity in the group of entities.

Abstract: A process for rendering a user interface for launching content for publication using a content management system (CMS), includes: providing, over a network, an editor application associated with the CMS, enabling editing of entities stored in the CMS, the editing includes authoring fields for each entity; providing, over the network, a launch application, wherein execution of the launch application renders the user interface for launching content for publication; receiving selection of a group of entities, via the user interface, the selection is for publishing the group of entities; and generating, responsive to the selection, an API call to the CMS, that triggers initiation of a validation process to validate each entity in the group of entities, wherein the validation process is executed in a draft entity store of the CMS that is created for said validation without requiring separate API calls for validating each entity in the group of entities.

Abstract: A non-transitory computer readable medium having program instructions configured, when executed by at least one server computer, to cause said at least one server computer to perform a method implemented in a content management system (CMS) for managing content types across multiple content spaces, said method including the following method operations: receiving, through a template creation interface, a selection of content types of a source content space; generating a template having said selection of content types, and storing said template to a template library; receiving a command to install the template into a destination content space; responsive to said command, installing the content types of the template into the destination content space, and establishing a link between the destination content space and the template such that the installed content types are identified as being managed via the template.

Abstract: A system for launching content for publication using a content management system (CMS) is provided. The system includes a server of a plurality of servers that is configured for enabling editing of entities using an editor application associated with the CMS. The editing includes authoring fields for each entity. The system includes a server of the plurality of servers that is configured for receiving selection of a group of entities, via a launch interface of the CMS. The selection is for publishing the group of entities. The system includes a server of the plurality of servers that is configured for generating, responsive to the selection, an API call to the CMS. The API call is defined to trigger initiation of a validation process to validate each entity in the group of entities. The validation process is executed in a draft entity store of the CMS that is created for said validation without requiring separate API calls for validating each entity in the group of entities.

Abstract: A method for launching content for publication using a content management system (CMS) is provided. Editing of entities is enabled using an editor application associated with the CMS, the editing includes authoring fields for each entity. A selection of a group of entities is received, via a launch interface of the CMS, the selection is for publishing the group of entities. Responsive to the selection, an API call to the CMS is generated, the API call is programmed to trigger initiation of a validation process to validate each entity in the group of entities, wherein the validation process is processed in a draft entity store of the CMS that is created for said validation without requiring separate API calls for each entity in the group of entities.