Created an about page, hid studies and participants and changed the footer text.

[sidpartha1]

Overview

• Fixing issue #29 The task required was to create an about page. To complete this I created a new component that should represent the about page and the contents inside of it.
• Created routing for the about page and included it in the navbar routing.
• Added message recognizing original creators and contributors in the about page
• At the moment about the component and home component almost look identical, but the home component is to be redesigned according to #30

Testing

• Manual testing methods were used to ensure that this component works as expected. The about page was visited from all routes possible e.g from all public pages, and all private pages. This was to ensure that the routing worked as expected and also to guarantee that the page rendered as expected.

• Advise if any new materials are to be added to the about page

What to look out for

• Should be able to access the page from anywhere, as long as the navbar is used

[sidpartha1]

Overview

• Fixing issue #18
• Updated footer to show "University of Auckland" as opposed to "by Dinal and Fraser", as per #18

Testing

• Manual testing was conducted for this issue. The application was launched and all pages that contained the footer were checked to ensure that the footer was visible and had the desired text.

What to look out for

• The footer should be visible and display the correct text without any additional changes as long as the footer component is used correctly.

[sidpartha1]

Overview

• Fixing issue #13

• Hid the studies and participants buttons until the users are logged in. This issue was tested manually, as it was a small issue. What was done was after adding the directive to the HTML files, the application was launched and all public pages were explored to ensure that the buttons could not be seen.

Testing

• After this, to make sure all the buttons were visible when logged in, there was a test conducted by logging in to both the USER and the ADMIN accounts. The buttons showed for both types of users and so the test was successful.

What to look out for

• If any new routes or pages are added pre-logout the buttons should still not appear as long as the navbar component is used correctly.

• If any new pages are added post-login, the buttons SHOULD be visible without any additional changes as long as the existing navbar component is used.

Completed issues #13 , #18 and #29

[softeng-701]

@sidpartha1 I am closing #13 #18 #29

[umih874]

The code looks well structured and modular. All the changes are working properly. I have reviewed these changes before they were approved by the softeng-701 team but I forgot to approve it. I added these changes to my repo so I can work on Issue #30 and I tested them before I started working on my issue but I forgot to approve these changes on here.