LO5 - Evaluation of the final Hive IT website.

Feedback

From the five people who have used my website, i noticed there were some fixes that needed to be made, but overall the feedback was extremely positive. Most people were impressed with the functionality of the site, as well as the simplicity of use. Users were also positive about the loading times and house style of the website. Testers were also impressed with the easy to access API and UI available for warnings towards your hive. Overall I believe that testers were impressed with the site and am happy with the feedback i have received. 

Evaluation

I (with the testers use in summary) have created an evaluation about the Hive IT website I have created.

Strengths:

• The website is simple to use for all ages, including children and people not as technology aware.
• The website uses state of the art PHP for a fast and easy display time from the user entering their Hive ID and receiving the results.
• The house style of the site is interactive and fun to view. Information is readily available and the theme goes with the connotations of bees and hives in general.

Weaknesses:

• I did not fully have enough time to program meta information and CSS for a completely responsive website, hence making the clouds stretch with different size browser resolutions.
• Some of the pages are not yet complete due to the need for more information with the Hive IT website. These pages do redirect to a nice 404 page however.
• The ID system needs a bit of work to select the most appropriate data to use for the graphs, at the moment it is picking the latest data.

Something that was desperately in need of changing was the home tab not working correctly on the 404 page. The code looked like this:

Unfortunately the function to detect the click in javascript was missing, so for that reason when the user clicked the open nav menu button then it did nothing rather than calling the css class to open the nav bar. To fix this i re-wrote the function that defined the variable 'body' as the body of the document, and then binded the click on the hamburger menu to toggle the class of menu open on the navigation bar. This triggered the menu to open through CSS transitions. Finally i retuned false to prevent anything extra from happening.