conzty01/RA_Scheduler

Update the UI to be consistent and appealing.

conzty01 opened this issue · 1 comments

Describe the bug
Currently, the UI is not very consistent between pages and also leaves a bit to be desired in terms of looks

To Reproduce
Switch between pages and you can see that the calendar is different sizes depending on what page you are on and that most of the time, you need to scroll to see the bottom. Resizing the window also can cause the calendar to draw over top of the navbar which does take up a bit of screen real estate unnecessarily

Expected behavior

  • The navbar should be moved to the top of the page where it can have a smaller footprint with dropdowns. (This will also allow us to implement new features more easily as they can be accessed in these menus.)
  • The size of the calendar should be consistent between each page.
  • Refactor the css that is formatting the calendar so that it does not live in the template itself.
  • Add API url to the environment variables so that we do not need to manually update values each time a new version is released to heroku.
  • The Manage Staff page should be updated so that adding a new staff member is hidden in a Modal.
  • The Manage Staff page should use the points calculated via the getRAStats method rather than from the ra table (soon to be depreciated)
  • In Chrome, the color selector in the Manage Staff page looks to be unusable even though it functions appropriately. (Perhaps editing a user should be pushed to a modal where it can be formatted more easily.
  • The modals on the Edit Schedule page are not formatted in a pleasing manner.
  • The "logo" for LC Res Life should be updated so that it is either an actual logo or a name more appropriate for this application
  • The RA points list on the Edit Schedule page shows a pointer on hover, however clicking the ra does nothing.

Screenshots
NA

Desktop (please complete the following information):

  • OS: Tested in Windows and Ubuntu
  • Browser: Chrome and Firefox

Smartphone (please complete the following information):
Not tested at this time, however this should be a consideration when updating the UI of this application

Resolved with PR #42