# Entando Blueprint Features

The Entando Blueprint leverages JHipster technology to quickly and easily create components for an Entando Application, including a Spring Boot microservice and corresponding micro frontends. The user specifies application parameters to autogenerate the project files via Embedded JavaScript (EJS), a templating language that provides powerful constructs for large-scale file generation. The following sections examine the features of the Entando Blueprint.

Follow the Entando Blueprint tutorial.

# Feature List

  • Backend with Spring Boot:
    • Data modeling
    • JHipster Design Language (JDL) support
    • Keycloak integration
    • Liquibase integration for schema upgrade
    • Preconfigured Cross-Origin Resource Sharing (CORS) settings
    • Profiles (dev, prod)
    • Swagger/OpenAPI frontend
  • Frontend with React:
    • .env profiles
    • Localization
    • Keycloak integration

# Preconfigured Micro Frontends

The creation of an entity using the Entando Blueprint generates the following preconfigured micro frontends. These are discussed in detail below.


  • The sample code and file paths on this page use Conference as the entity name.
  • Custom element names require a hyphen, e.g. conference-details (kebab-case).

What the micro frontends have in common:

  • Each micro frontend contains a README file to assist with its setup.
  • All generated micro frontends are web components created using the custom elements API.
  • Each micro frontend is displayed using the custom element tag, e.g.:
    • The details widget file microfrontends/conference-details/public/index.html contains conference-details id="1" override-edit-handler hide-edit-button />.
    • The element <conference-details /> is defined as a component entry in microfrontends/conference-details/src/custom-elements/ConferenceDetailsElement.js.

For more information about web components, custom elements and micro frontends, refer to Create a React Micro Frontend.

# Authentication

  • If a widget requires authentication, the component is wrapped in KeycloakContext.Provider and the Keycloak object is fetched from the window.entando.keycloak variable.
  • Entando allows Keycloak to be replaced with another authentication provider as needed.
      <KeycloakContext.Provider value={this.keycloak}>
        <StylesProvider jss={this.jss}>
          <ThemeProvider theme={this.muiTheme}>{FormContainer}</ThemeProvider>

For more information on Keycloak and authentication with Entando, refer to the Entando Identity Management System.

# Custom Events

  • All MFEs rely on custom events for communication. Consequently, each MFE is able to create or remove custom events and event listeners.
  • An event listener should be created in the custom element’s disconnectedCallback() function, and only when the element is no longer needed.
  • To add an event to the listener list, add the event type to the INPUT_EVENT_TYPES object at microfrontends/conference-details/src/custom-elements/widgetEventTypes.js. To remove an event listener, simply remove the element from the list.

Refer to Communicate Between Micro Frontends for more information about custom events and MFE communication.

# Tests and Mocks

  • Tests have been written for each preconfigured MFE using react-testing-library. These can be updated via a preferred developer tool.
  • The tests and mocks for each micro frontend are located in its /src/components/ directory.

# PropTypes

  • PropTypes for data used across several components are available to view or modify at microfrontends/conference-details/src/components/.
  • These are shared resources and can be imported into components to avoid the repetition of definitions, e.g.:
    import React from 'react';
    import conferenceType from 'components/__types__/conference';
    const ConferenceDetails = props => {
      // ...
    ConferenceDetails.propTypes = {
      conference: conferenceType,
      t: PropTypes.func.isRequired,
    export default ConferenceDetails;

# Fetching Data

  • To fetch data from widgets, use Fetch API (opens new window).
  • Data fetching functions are organized by context in the files found at microfrontends/conference-details/src/api.

# Form Widget