nofusscomputing / nofusscomputing/centurion_ui

Production Usage

Open
#171 0 comments 0 reactions 1 assignee View on GitHub

@jon-nfc is already working on this.

Since May 1, 2026.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1d 4h
Merged PRs (30d)
20

Description

Summary

This ticket is the single point of information and for tracking work required for production usage of Centurion UI.

Description

Centurion UI is being developed alongside Centurion ERP. This allows for development of the backend to drive what is required for a dynamic frontend. As such and initially Centurion UI wont be production ready due to the backend being Django using the Django Rest Framework (DRF).

Business Value / Objectives

A truly dynamic frontend reduces overhead, technical debt and development costs.

Success Criteria
  • Clearly defined backend-frontend API
  • Dynamic frontend that works with any backend.
  • Test coverage > 85%
Scope

In scope only covers what is required to achieve the objectives of this epic

Dependencies

No response

Risks & Mitigations

No response

Stakeholders / Roles
  • Backend developers
  • Backend owners
  • Frontend developers
  • Frontend owners
  • webmasters
Milestones / Timeline

To move towards Centurion UI being truly dynamic and for any backend production readiness will occur in the following stages:

  1. Functional frontend for Centurion ERP

  2. Functional frontend for Django with DRF

  3. Functional frontend for any backend

Stage 1

Get the frontend fully working for Centurion ERP

Stage 2

Refactor frontend making any Centurion ERP specifics dynamic with end state being Centurion UI can work with any Django DRF backend

Linked Features / Stories (Task List)
  • ...
Additional Notes / References

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.