search

arangace / CreamCat

SOFTENG750 project team CreamCat
MIT License
0 stars 3 forks source link

Frontend developed #4

Closed arangace closed 3 years ago

arangace commented 3 years ago

Created a deployable frontend with a skeletal structure

arangace commented 3 years ago

@arangace Is this code written to be just a dummy frontend with no functionality? Since there is not route switch frontend/src/App.js to handle URL changes yet.

Also, frontend/package.json still contains info from where it was copied from and needs customization.

If this is meant to just be a dummy frontend then there should be no problem merging the current code. However, it might benefit us to create a merge/frontend branch and implement at least some route handling before merging into develop. Just to keep our workflow mint and clean.

yes as we haven't fleshed out the functionality we want on the pages yet, i've just floated some ideas of what we could have. Everyone being able to run this on their local copy is the motive. As per the URL changes, it depends if we want a single page application or a multiple page application depending on how we want to handle different pages i've left that the same for now. I can create skeletal pages for the filler links. As for the frontend/package.json i'm unsure which is actually being used and which is depreciated, if you would like to clean it up then I think it should be fine otherwise i'm not really sure.