Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate the API and UI into two distinct services #223

Open
kenellorando opened this issue Feb 15, 2023 · 0 comments
Open

Separate the API and UI into two distinct services #223

kenellorando opened this issue Feb 15, 2023 · 0 comments
Assignees
Labels
domain: cadence-api Relates to cadence API domain: cadence-ui Relates to cadence UI

Comments

@kenellorando
Copy link
Owner

The Cadence API server currently runs a Go fileserver which serves raw HTML, CSS, and JavaScript. It's simple and looks fine to me, but I think it's time we separate the services. As the number of API calls grows, so too does the management of the raw UI components built by hand that drive the frontend.

Separation might help for a potential UI overhaul using a modern JavaScript web development framework. Possibly with Vue or Svelte. Whatever it is, we want it to be easy to re-implement a theme changer. Present v5's UI is built with the Bulma library which is simply too difficult to style with pure as in pure CSS. Additionally, separation of services would allow the API and UI to be deployed and scaled independently.

@kenellorando kenellorando added domain: cadence-ui Relates to cadence UI domain: cadence-api Relates to cadence API labels Feb 15, 2023
@kenellorando kenellorando self-assigned this Mar 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: cadence-api Relates to cadence API domain: cadence-ui Relates to cadence UI
Projects
None yet
Development

No branches or pull requests

1 participant