Abstract: A system for managing a content management system (CMS), including, a plurality of servers for hosting the CMS, the CMS is accessed via a web editor that is executed on a client browser and provides access to functionality of the CMS for defining a content project, the web editor further provides access to an APP marketplace, the APP marketplace providing access to a plurality of APPS which can be added to the content project for use via the web editor; a server-side web editor configured to receive data indicating selection to add an APP to the content project, wherein responsive to launching editing of the content project in the web editor, then the APP is launched in accordance with an application framework that causes assignment of an identity to the APP for making content management API calls to the CMS for creating and editing structured content of the content project.

Abstract: A non-transitory computer-readable medium having program instructions embodied thereon, said program instructions configured to, when executed by at least one server computer, cause said at least one server computer to perform a method for activating editing functionality in a content management system (CMS), said method including the following operations: the CMS providing a content management application programming interface (CMA) enabling management of a content project, the content project having a content model defined by a plurality of content types, each content type defining one or more fields, said content types defining structures for content managed via the CMS; responsive to an application programming interface (API) call to the CMA, then assigning one or more annotations to one or more of the content types; wherein for the content types having annotations assigned thereto, the assigned annotations enable an editing functionality of an editing application interfaced with the CMS.

Abstract: A method implemented in a content management system (CMS) is provided, for providing integration between APPS configured for use with an editor application of the CMS, including: installing a first APP and a second APP in a content project of the CMS, wherein installing the first and second APPs enables functionalities of the first and second APPs to be accessed for the content project through the editor application, wherein the editor application provides an interface for editing the content project; receiving from the first APP a request to invoke an action by the second APP; responsive to receiving the request, then validating contents of the request; responsive to successful validation of the request, then sending an acknowledgement to the first APP, and generating a call to the second APP to invoke the action by the second APP.

Abstract: A content management system (CMS) provides integration between APPS configured for use with an editor application of the CMS, the CMS including at least one server computer configured to perform the following operations: installing a first APP and a second APP in a content project of the CMS, wherein installing the first and second APPs enables functionalities of the first and second APPs to be accessed for the content project through the editor application, wherein the editor application provides an interface for editing the content project; receiving from the first APP a request to invoke an action by the second APP; responsive to receiving the request, then validating contents of the request; responsive to successful validation of the request, then sending an acknowledgement to the first APP, and generating a call to the second APP to invoke the action by the second APP.

Abstract: A non-transitory computer-readable medium having program instructions for a method implemented in a content management system (CMS), for providing integration between APPS configured for use with an editor application of the CMS, the method including the following operations: installing a first APP and a second APP in a content project of the CMS, wherein installing the first and second APPs enables functionalities of the first and second APPs to be accessed for the content project through the editor application, wherein the editor application provides an interface for editing the content project; receiving from the first APP a request to invoke an action by the second APP; responsive to receiving the request, then validating contents of the request; responsive to successful validation of the request, then sending an acknowledgement to the first APP, and generating a call to the second APP to invoke the action by the second APP.

Abstract: A method performed by a CMS and an edge node of a CDN is provided, including: sharing a server secret between the CMS and the edge node; using, by the CMS, the server secret to generate a signing key, the signing key being transmitted to a client system, wherein the client system receives a request for a content item from a user device, and wherein the client system uses the signing key to generate a signed URL for the content item, the user device being redirected to the signed URL; responsive to receiving the signed URL from the user device, then validating the signed URL by the edge node, wherein validating the signed URL uses the server secret to rederive the signing key based on the signed URL; responsive to successful validation of the signed URL, then providing the content item from the edge node to the user device.

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 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: 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 system for editing content of a content management system (CMS) includes providing an editor application that provides an interface for composing a content page in the CMS. The content page is associated with a plurality of content components referenced in the content page which are further arranged in accordance with a logical hierarchy defined for the content page. A graphical tree view is displayable via the interface, and presents content components in accordance with the logical hierarchy, wherein each of said content components is selectable via the graphical tree view. An editing view in the interface is responsive to selection of one of the content components from the graphical tree view, and provides access to editing fields related to the selected content component. The editing view presented maintains a correlation to a relationship position of the selected content component in the logical hierarchy.

Abstract: A process for rendering a user interface for a content management system (CMS) includes: providing, over a network, the user interface for rendering through a browser of a client device; the user interface enables configuring a content project including a content model, the content model defining content types for the content project; wherein content entries are defined according to the content types, wherein each content entry is structured in accordance with a given content type, so that multiple content entries are defined from a given content type; wherein the user interface enables a tag to be set in association with any of the plurality of content entries; and wherein the CMS exposes a content delivery API (CDA) that enables, through a single API call to the CDA that references the tag, retrieval of the content entries across the plurality of content types that have the tag set in association therewith.

Abstract: A method and a content management system (CMS) that enable storage and retrieval of structured content are disclosed. In one example, CMS includes means for configuring a content project. The content project includes a content model, and the content model defines a plurality of content types for the content project. The CMS includes a plurality of content entries defined according to the content types. Each content entry is structured in accordance with a given content type from which the content entry is defined. Multiple content entries are defined from a given content type. The CMS includes at least one tag configured to be set in association with any of the plurality of content entries. The method includes means for exposing a content delivery API (CDA) configured to enable, through a single API call to the CDA that references the tag, retrieval of the content entries across the plurality of content types that have the tag set in association therewith.

Abstract: A method for editing content of a content management system (CMS) includes providing an editor application that provides an interface for composing a content page in the CMS. The content page is associated with a plurality of content components referenced in the content page which are further arranged in accordance with a logical hierarchy defined for the content page. A graphical tree view is displayable via the interface, and presents content components in accordance with the logical hierarchy, wherein each of said content components is selectable via the graphical tree view. An editing view in the interface is responsive to selection of one of the content components from the graphical tree view, and provides access to editing fields related to the selected content component. The editing view presented maintains a correlation to a relationship position of the selected content component in the logical hierarchy.

Abstract: A process for rendering a user interface for editing content of a content management system (CMS), includes: providing, over a network through a browser of a client device the user interface, the user interface is configured for editing a content page in the CMS; presenting a graphical tree view in the user interface that presents content components, wherein the graphical tree view of the content page provides a parallel structure to content presentation of a website page that implements API calls to the CMS for accessing content edited for the content page; and presenting an editing view in the user interface responsive to selection of one of said plurality of content components from the graphical tree view; wherein the editing view presented maintains a correlation to a relationship position of the selected content component in the logical hierarchy defined for the content page.

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 that provides access to applications that integrate with a content management system (CMS), includes: providing a content management API configured to enable creating or updating a content project; receiving a command to enable an APP for the content project, wherein the APP includes a front-end component; providing, over a network, a web editor of the CMS to access the content project, wherein the APP and the front-end component are launched in an APP runtime environment of a client browser that is independent of a web editor runtime environment in which the web editor is executed, and wherein the execution of the web editor renders the user interface, and the service provided by the APP is visually integrated with services of the web editor in a predefined context of the user interface.

Abstract: A method and a content management system (CMS) that enable storage and retrieval of structured content are disclosed. In one example, CMS includes means for configuring a content project. The content project includes a content model, and the content model defines a plurality of content types for the content project. The CMS includes a plurality of content entries defined according to the content types. Each content entry is structured in accordance with a given content type from which the content entry is defined. Multiple content entries are defined from a given content type. The CMS includes at least one tag configured to be set in association with any of the plurality of content entries. The method includes means for exposing a content delivery API (CDA) configured to enable, through a single API call to the CDA that references the tag, retrieval of the content entries across the plurality of content types that have the tag set in association therewith.

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 process for rendering a user interface of a web portal providing access to content of a content management system (CMS) includes: providing, from a client system of the CMS, the user interface for rendering through a browser of a user device; receiving, by the client system from the user device via the user interface, a request for a content asset; sharing a server secret between the CMS and an edge node; using, by the CMS, the server secret to generate a signing key, transmitted to the client system, wherein the client system uses the signing key to generate a signed URL for the content asset, the user device being redirected to the signed URL; responsive to receiving and successful validation of the signed URL by the edge node, then providing the content asset from the edge node to the user device for presentation through the user interface.