US 11,741,184 B2
Systems for launching content for publication
Bruce Felt, Berlin (DE); Benjamin Keyser, Berlin (DE); Paolo Negri, Berlin (DE); Stephan Schneider, Berlin (DE); and Thomas Spiesser, Berlin (DE)
Assigned to Contentful GmbH, Berlin (DE)
Filed by Contentful GmbH, Berlin (DE)
Filed on Aug. 15, 2022, as Appl. No. 17/887,767.
Application 17/887,767 is a continuation of application No. 17/471,152, filed on Sep. 9, 2021, granted, now 11,436,300.
Application 17/471,152 is a continuation of application No. 17/202,142, filed on Mar. 15, 2021, granted, now 11,409,835, issued on Aug. 9, 2022.
Application 17/471,152 is a continuation of application No. 17/201,854, filed on Mar. 15, 2021, granted, now 11,210,364, issued on Dec. 28, 2021.
Prior Publication US 2022/0391458 A1, Dec. 8, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 16/958 (2019.01); H04L 67/55 (2022.01); H04L 67/02 (2022.01); G06F 16/93 (2019.01); G06F 16/176 (2019.01)
CPC G06F 16/958 (2019.01) [G06F 16/176 (2019.01); G06F 16/93 (2019.01); H04L 67/02 (2013.01); H04L 67/55 (2022.05)] 20 Claims
OG exemplary drawing
 
1. A process for rendering a user interface for launching content for publication using a content management system (CMS), comprising:
providing, over a network, an editor application associated with the CMS, the 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, via the reference tree of the user interface, the selection is for publishing the group of entities; and
generating, responsive to the selection, an application programming interface (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, without requiring separate API calls for validating each entity in the group of entities; 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 entities.