# Entando Blueprint Features

The Entando Blueprint is an easier and faster way to customize your application by generating controllers, repositories, services, and micro frontends for your entity. The project files are generated in minutes, by entering data that define the parameters of your application.

The Entando Blueprint uses JHipster technology based on Embedded JavaScript (EJS), a templating language that provides powerful constructs for large scale file generation.

# The Features:

  • 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

For more information:

# Premade Micro Frontends

When you create an entity using the Entando Blueprint, it generates a few premade MFEs. Each will be reviewed below.

We will be using Conference as an entity name for the example below.

What the micro frontends have in common:

  • Each MFE contains a README file that helps with the setup.

  • All generated micro frontends are web components created using Custom Elements API.

  • Each MFE is displayed using the custom element tag. For example, inside the details widget folder microfrontends/conference-details/public/index.html, you can find conference-details id="1" override-edit-handler hide-edit-button />. The element <conference-details /> is defined in the component entry point at microfrontends/conference-details/src/custom-elements/ConferenceDetailsElement.js.


Custom element names require a hyphen like conference-details (kebab-case)--they cannot be single words.

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 uses Keycloak as the authentication provider, but you can add any provider as needed.

  <KeycloakContext.Provider value={this.keycloak}>
    <StylesProvider jss={this.jss}>
      <ThemeProvider theme={this.muiTheme}>{FormContainer}</ThemeProvider>

For more information about the authentication process, please refer to the Authentication section.

# Custom events

All MFEs rely on custom events for communication. That is why each MFE contains custom event creation and removal, along with the event listener creation. Note that when an event listener is created, it should be when the element is no longer needed. It should be created in the custom element’s disconnectedCallback() function.

To add more event listeners, add the event types to INPUT_EVENT_TYPES object at microfrontends/conference-details/src/custom-elements/widgetEventTypes.js, which adds it to the listener list. To remove the event, simply remove the element from the list.

For more information about custom events and MFE communication, please refer to the page Communicate Between Micro Frontends.

# Tests and Mocks

Each MFE has tests written for it. Entando uses react-testing-library, but developers are free to upgrade and use any tool desired. Tests and mocks for each micro frontend are located in its /src/components/ directory.

# PropTypes

PropTypes for data used across several components are shared. You can see and modify them at microservices/conference-details/src/components/. This way you can avoid repeating the same propTypes in each component by importing them.

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

For data fetching from widgets, use Fetch API. You can find the functions for fetching data at microfrontends/conference-details/src/api, in different files for different contexts.

# Form widget

For displaying forms within a widget, use Formik (opens new window) which helps with form state management. For data validation, use Yup (opens new window).