nofusscomputing / nofusscomputing/centurion_ui

Planning Document: feature release (v0.15.0 expected)

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

@jon-nfc is already working on this.

Since Sep 10, 2026.

  • #256 by @jon-nfc — merged
Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1d 4h
Merged PRs (30d)
20

Description

Prior to this release there has been limited project management. As such, a lot of work has created countless bugs (lack of tests) and there has been no clear path forward. This release is the beginning of improving the project management

Goals

  • Ongoing - Refactor js(x) -> ts(x) - #174
  • Obgoing - Define backend<>frontend spec - #152
  • Proper project management
  • Demo Deployment of current working branch, feat-next-release.
    API Docs to link to to show what object looks like.

⚖️ Order of Work / Tasks

  1. Backend driven routing

    Routes built from data the backend provides.

  2. Backend driven navigation

    • #143
  3. Dynamic Backend Features

    Backend does not provide, they dont display within the interface.

    • Settings
    • Notifications
  4. Restructure / Rename of page features

    • move Layout -> View

      Currently the layout is not really a layout, but a view of different objects. These objects should be complete on their own so that they can be used outside of a view. As an example, if you wanted to make tickets show in a pop-up you would include the ticket view in a pop-up..

    • Add Layout

      _A Layout is that for how the content will be laid out. i.e. Tabbed, sidebar, etc _

  5. Finalise Layouts

    • List
    • Detail
    • Ticket
  6. Finalise Components


Links

Nil Response.

Tasks

  • Investigate -> https://swr.vercel.app/

    does caching

  • Add Feature - UI unable to work on sub-path as the asset links are not relative so js and css fail to load.

Requirements

  • Any file that is created must be typescript.

  • Every object must be fully API documented

    • Components that create UI objects has a link to demo docs.

🏁 Roadmap

Completed
♾️ In the future

⌚ Tech Debt

Items listed as part of this tech debt area are items / objects that require refactoring. As such no new features are to be added to them until the tech debt is cleared.

  • #108
  • #174
  • #177
  • #205
  • #210

🐛 Outstanding Bugs

  • #99

  • #186

  • #194

  • #195

  • #199

  • #200

  • #255

  • #258

  • #262

  • #263

  • #265

  • #266

🪓 Outstanding Backlog

This section contains items from the backlog that are considered priority

  • #174

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.