nofusscomputing / nofusscomputing/centurion_ui

Common UI

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

@jon-nfc is already working on this.

Since Mar 4, 2026.

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

Description

Summary

Creation of a Common UI

Description

Currently the UI is functional however must be refined so as to reduce tech debt. This'll be done by implementing the PatternFly Design system along with any new components that are required so as to ensure that the UI can meet the needs of Centurion ERP.

Although the UI is for Centurion ERP the intent is that this UI could be used by any backend that supplies the correct API features that this UI system requires to render a UI.

Business Value / Objectives
  • refactor current components to use the PatternFly System
  • Documentation of the Dynamic UI API specification
Success Criteria
  • PatternFly Design system used
  • Has Detail page
  • Has List page
    • can filter
    • can search
    • can "order By" i.e. change column order
    • paginated
  • Has ticket page
  • Has "new" object page
  • has settings page
  • Mobile browser usable
  • light/dark mode support
  • Dynamic UI API documented
  • When drawing page, utilises allow header from HTTP Response
Scope
  • Current features refactored
Dependencies
  • #118
Risks & Mitigations

No response

Stakeholders / Roles
  • Developers
Milestones / Timeline
  1. Menu / Navigation
  2. List page
  3. Detail Page
  4. Ticket Page
Linked Features / Stories (Task List)
  • #120

  • #121

  • Common Page

  • #128

  • Detail View

  • Ticket View

  • Clean-up / Remove Files

    • src/index.css
  • Allow response header usage
    i.e. if POST is present, then user can "create"..... _ so on for other HTTP methods_

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.