You’re making a site with (what appears to be) multiple pages. There should be c

You’re making a site with (what appears to be) multiple pages. There should be common elements
(notions of theming, banners, etc.) across the site. There will be several primary pages: a Home
page, displaying basic information about yourself (background, research/academic interests); a
Courses page, which displays a list of courses you are currently taking (or a longer list of all
courses you have taken); an About me, which provides a deeper summary of you and your interests (they may even be hobbies!), a CV page, which displays the latest version of your CV (this may be just a pretty and high resolution image of a CV you already have, or you can format it as textual display on the webpage itself).
Now, as additional pages (these one naturally may not always be expected from a personal webpage, so feel free to remove these later when completing your own professional pages), you will have a Past Projects page, in which you may include links to past projects you have completed, but must, crucially, include links to your past four assignments in our class.
Relating to this page, you will have a sign-up and log-in button (can be alongside the menu that
takes you to the mentioned sections of your website), which allows users on your website to signup/log-in in order to access the content in your Past Projects page. In addition, if the user is not currently logged in, your Past Projects page will always succeed a login form (otherwise they will be directed to it automatically), where the user must enter a valid (i.e., registered) username and password to access the page. If they fail, they are prompted with some error and may retry. I’m
asking you to use asynchronous communication for this.
Security: We don’t want the user to need to log-in every time they want to visit your Past Projects.
As shown in lecture 19, this can be accomplished by passing the username and password to this
page, after having logged in once, with the magic of PHP and hidden forms. However, this isn’t very secure as this information will be transferred through packets upon every request; I am therefore wanting you to store the username and password locally on the client side using session storage (and not web storage) in order for it to neither be transferred nor be permanent.
You should not use this template of mine as a copying mechanism, and I’m asking the TAs to pay
attention to that, but you can use my personal webpage here as an aesthetic example of what a
themed personal webpage could look like: http://cosc.brocku.ca/~aemami/. Obviously, it doesn’t
abide by a lot of the requirements for this assignment.
Your webpage should also be responsive – again, responsive design means that your webpage must work on different display sizes. Your web page must work, as a minimum, on cellphone, tablet and desktop display sizes. The TA will test this by reducing the browser window size on their PC. The TA will not actually test on a cellphone or a tablet.
BONUS (see rubric): Now, what if I asked you to do this all in a single .html file (a single page)?
You may also see this as having 1 .html file and 1 .php file, or a single .php file. Also, what if you
stored a ticket (randomly generated string) for each username/password pair in session storage?