US 11,783,294 B1
Templates for content spaces in a content management system
Paolo Negri, Berlin (DE); Andrew Grant, Berlin (DE); Farruco Sanjurjo, Berlin (DE); Thomas Spiesser, Berlin (DE); and Grace Gross, Berlin (DE)
Assigned to Contentful GmbH, Berlin (DE)
Filed by Contentful GmbH, Berlin (DE)
Filed on May 11, 2022, as Appl. No. 17/742,293.
Application 17/742,293 is a continuation of application No. 17/742,178, filed on May 11, 2022.
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 9/44 (2018.01); G06F 9/455 (2018.01); G06F 9/445 (2018.01); G06Q 10/101 (2023.01); G06F 40/186 (2020.01); G06Q 10/10 (2023.01); G06F 8/61 (2018.01)
CPC G06Q 10/101 (2013.01) [G06F 8/61 (2013.01); G06F 40/186 (2020.01); G06Q 10/103 (2013.01)] 15 Claims
OG exemplary drawing
 
1. A content management system (CMS) configured for managing content types across multiple content spaces in the CMS, said CMS comprising at least one server computer, said at least one server computer being configured to implement the following method operations:
receiving, through a template creation interface, a selection of a plurality of content types of a source content space in the CMS, wherein the plurality of content types do not store content of the source content space;
generating a template having said selection of said plurality of content types, and storing said template to a template library;
receiving a command to install the template into a destination content space in the CMS;
responsive to said command, installing the plurality of 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, wherein installing the content types of the template includes performing a validation process to verify compatibility of the template with the destination content space;
providing an editor interface of the CMS that enables access to edit content of the destination content space;
receiving, through the editor interface of the CMS, a command to create a content entry based on one of the installed content types; and
responsive to the command to create the content entry, then generating and storing the content entry in the destination content space in the CMS, said content entry having one or more fields as defined by the one of the installed content types, wherein the installed content types do not store the content of the destination content space, and wherein said content entry is configured to store the content of the destination content space for delivery to a presentation context when retrieved from the CMS.