Systems and methods for developing digital experience applications

A computer-implemented method for developing a digital experience application using a developer utility framework, the method comprising the following operations performed by at least one processor:

• sending, from a command line interface of the developer utility framework, a plurality of commands to create a driver application comprising a runtime shell distinct from a micro-application, a page component of the driver application wherein the page component comprises layout configuration information defining named regions and router configuration information, and a first micro-application as a separate build output;
• receiving, at a build tool of the developer utility framework, the plurality of commands, wherein the build tool is further configured to:
• create, as separate build artifacts, the driver application, the page component, and the first micro-application;
• and
• generate a composition manifest that maps micro-applications to the named regions defined by the layout configuration information;
• creating, using the build tool of the developer utility framework, the driver application;
• creating, using the build tool of the developer utility framework, the page component of the driver application;
• creating, using the build tool of the developer utility framework, the first micro-application;
• appending, using the build tool of the developer utility framework, the first micro-application to the page component of the driver application by associating the first micro-application with a named region via the composition manifest;
• and
• storing, at a micro-application portal of the developer utility framework, the first micro-application,
• wherein the driver application is configured to host and manage a plurality of micro-applications including registration, initialization, activation, and deactivation of the micro-applications,
• wherein the driver application comprises an event hub and a state store to route event information and state information among the plurality of micro-applications, and
• wherein the page component comprises layout configuration information to lay out a plurality of micro-applications.

A tangible, non-transitory computer-readable memory device that stores a set of instructions that, when executed by at least one processor, cause the at least one processor to perform operations comprising:

• sending, from a command line interface of the developer utility framework, a plurality of commands to create a driver application comprising a runtime shell distinct from a micro-application, a page component of the driver application wherein the page component comprises layout configuration information defining named regions and router configuration information, and a first micro-application as a separate build output;
• receiving, at a build tool of the developer utility framework, the plurality of commands, wherein the build tool is further configured to:
• create, as separate build artifacts, the driver application, the page component, and the first micro-application;
• and
• generate a composition manifest that maps micro-applications to the named regions defined by the layout configuration information;
• creating, using the build tool of the developer utility framework, the driver application;
• creating, using the build tool of the developer utility framework, the page component of the driver application;
• creating, using the build tool of the developer utility framework, the first micro-application;
• appending, using the build tool of the developer utility framework, the first micro-application to the page component of the driver application by associating the first micro-application with a named region via the composition manifest;
• and
• storing, at a micro-application portal of the developer utility framework, the first micro-application,
• wherein the driver application is configured to host and manage a plurality of micro-applications including registration, initialization, activation, and deactivation of the micro-applications,
• wherein the driver application comprises an event hub and a state store to route event information and state information among the plurality of micro-applications, and
• wherein the page component comprises layout configuration information to lay out a plurality of micro-applications.