This documentation is for the version of Entando currently under development and is a work in progress. Some screenshots or references to the previous version may be out-of-date and some documented features may only be available by building from source.
# Entando Platform
Entando is the leading open source Application Composition Platform for Kubernetes. It enables parallel teams to accelerate development and innovation of business capabilities on a modern, cloud-native, and Kubernetes-native stack.
It is a distributed and composable environment in which components can be built, scaled and iterated independently, helping teams build agile applications that can adapt to change.
On the Entando Platform, development of an application is organized into four stages: Create, Curate, Compose, and Consume. In the simplest terms, you create functional building blocks, curate them into a catalog, compose the blocks onto an app or website, which is then consumed by a user. The Enterprise Architect oversees the process, defining business domains and mapping the capabilities for the building blocks.
# Create Components
The first step in building a modern application on Entando is to design and create each independent component or functional block. Developers can use the Entando Component Generator and Blueprint to automate the building and packaging of project files, with the flexibility to customize while using software they are accustomed to. The modular design of apps built on Entando means new business capabilities can be integrated into your application without reworking existing systems.
|Entando Component Generator||Micro Frontends|
|Entando Blueprint Feature||Microservices|
|Component Generation Technologies||Build and Publish Project Bundles|
# Curate and Share Components
On the Entando Platform, Curate and Share means development teams can bundle and share components within a central catalog. Multiple teams can collaborate on a single component or packaged business capabilities (PBCs) and share them across organizations and applications. They can test and assess components for readiness, manage and publish versions, and share metadata for continuous upgrades.
# Compose an Application
The Compose stage is centered around the Entando App Builder, a low-code composition user interface. In the App Builder, application owners can assemble new components or upgrade existing ones with templates, widgets and PBCs. The Entando Component Manager and Local Hub are integrated into the App Builder to manage your components, making the process flexible and agile.
|Welcome Wizard||Page Management|
|Local Hub||Widgets and Fragments|
|Entando App Builder||Content Creation|
|Entando Component Manager||Content Templates|
# Consume Applications
In the development lifecycle of an application, Consume is the execution stage where users interact with the app. On Entando, the modular design of components and services means they can be scaled individually, or as a whole, according to those interactions. Likewise, content can be updated, engine rules adapted, and upgrades carried out seamlessly. As a result, the development cycle is a continuous process with minimal disruptions and faster time to market.
|Accessibility||High Availability on Entando|
|Entando Operator||Add an API Claim|
|Entando APIs||Invoke Entando core APIs|
|Entando Identity Management System||External Identity Management System|