Centurion UI

---

---

---

Centurion UI is a metadata-driven frontend that renders and interacts with structured data provided by backends such as Centurion ERP. Unlike traditional UIs, it does not handle security or business logic — those remain fully on the backend. The UI’s role is to interpret and display data as views, pages, and components, letting users focus on using applications rather than building interfaces.

Components of Centurion UI

For Centurion UI to function dynamically, metadata that Centurion UI requires must be in an expected format. To aid in this we have broken down each area of that metadata so that its easier to parse. Those areas are:

• User Interface

• Setup Centurion UI

  How to setup Centurion UI for your backend.

• Backend Metadata

  What and how your backend should provide for Centurion UI to function.

• Navigation

  Metadata structure for providing UI navigation.

• User Details

  Metadata structure for providing user details.

• View Layout

  Metadata structure for providing the layout that will be rendered.

• Field Types

  Metadata structure for providing the different field types that the UI can handle.

  • Makrdown

• URLs

How It Works

Centurion UI treats data much like a database client:

• A view is determined by the data received: a single row, a subset of rows, or a full dataset.
• Components on a page use either cached data or additional API queries, depending on the user’s permissions.
• Users or IT teams can create new components and dashboards from available data without writing frontend code.

This approach ensures that adding new features to your backend requires no UI changes, saving time and effort. Components, pages, and dashboards update automatically whenever backend data or structure changes.

Development Philosophy

The UI is being developed in parallel with Centurion ERP, allowing the specification of the interface to be refined through real-world use. This ensures that:

• Views, components, and interactions are validated as the backend evolves.
• The UI remains adaptable and backend-agnostic.
• Development teams can focus on building features rather than rewriting interfaces.

Additional information related to development can be found in its docs.

Vision

The goal of Centurion UI is to provide a flexible, universal frontend platform that works with any backend and any type of user. By separating rendering from security and business logic, the UI allows teams to build, update, and extend applications quickly, all through one interface.

Key benefits include:

• Add backend features without changing the UI
• One UI, multiple backends—future-ready and adaptable
• Dynamic pages and dashboards built from live data
• Custom components and visualizations without coding
• Faster development, less maintenance, more focus on delivering value

Centurion UI is designed to make data and features instantly usable, accessible, and adaptable for every user and workflow.

About:

This page forms part of our Project Centurion ERP UI.

Page Metadata

Version: ToDo: place files short git commit here
Date Created: 2024-09-27
Date Edited: 2026-05-17

Contribution:

Would You like to contribute to our Centurion ERP UI project? You can assist in the following ways:

• Edit This Page If there is a mistake or a way you can improve it.
• Add a Page to the Manual if you would like to add an item to our manual
• Raise an Issue if there is something about this page you would like to improve, and git is unfamiliar to you.

 

ToDo: Add the page list of contributors