Unified Admin

It was essential for us to create an admin that was flexible enough to work with any headless API we throw at it. Not only is this important for our internally developed services, but this is important for our customers, who often have existing services that they may want to centrally manage.

It was essential for us to create an admin that was highly extensible. Our out-of-box admin screens and services often work as they come for many customers, but when they do not, it is important to provide ways to customize. We have put a lot of work into creating intuitive and powerful ways to extend and customize the admin to fit business needs.

It was essential for us that we keep up on the latest technologies and best practices. We chose to use React with modern tooling for our frontend, and the latest of Spring Boot for many of our services.

The frontend admin client written in React. This is a single-page application responsible for rendering the admin within a user’s browser. See the Admin Client section for more on the admin client.

The services used to support different parts of the admin application.

The service responsible for providing expressive metadata as JSON that is used to drive the content and layout of the admin views and forms. See the Metadata section for more on the metadata service.

The service responsible for providing the navigation hierarchy for the admin. See the Admin Navigation Services section for more on the navigation service.

The OAuth2 authorization server responsible for issuing access tokens for accessing Broadleaf Services.

The services Broadleaf provides that the admin is pre-configured to manage and interact with.

The services you choose to expose and manage from within the admin application.