Skip to content
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.

Combine Frontends into Same Directory #276

Open
erotondo opened this issue May 5, 2021 · 1 comment
Open

Combine Frontends into Same Directory #276

erotondo opened this issue May 5, 2021 · 1 comment
Labels
Backlog A backlogged issue that still needs to be completed Doge frontend Editor An issue related to the editor component of the software Frontend An issue handled by the frontend developers Git-Kings Frontend

Comments

@erotondo
Copy link
Collaborator

erotondo commented May 5, 2021

Combine the two frontends into one directory

  • While not necessary, this is probably a good idea. It will also make routing between the two frontends from the login process a lot easier.

BACKLOGGED: Ran out of time to implement; needed to focus on integrating with the backend team to set up new endpoints that worked with the new schema before deploying changes to the server.

@erotondo erotondo added Doge frontend Git-Kings Frontend Backlog A backlogged issue that still needs to be completed Frontend An issue handled by the frontend developers Editor An issue related to the editor component of the software labels May 5, 2021
@erotondo
Copy link
Collaborator Author

erotondo commented May 5, 2021

This is a recommended but not required issue. However, this likely should be done considering how the hope for the software is to make it eventually deployable across UMass Amherst and other universities.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Backlog A backlogged issue that still needs to be completed Doge frontend Editor An issue related to the editor component of the software Frontend An issue handled by the frontend developers Git-Kings Frontend
Projects
None yet
Development

No branches or pull requests

1 participant