Skip to content

heathornJ/localBusinessCafe

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

45 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Overview

Welcome to my front end software developer project for "Local Business Café". This README file provides information about the content, creation, and learning process involved with creating this site.

Introduction

The website acts as advertisement and a source of information for customers regarding the cafe. They can learn about the business, get in contact/read faqs, look at the menu, and browse the cafe's shop.

User Stories

First Time Visitor Goals:

  • As a first-time vistor, I want to know immediately what company the website is for.
  • As a first-time visitor, I want to easily navigate the website.
  • As a first-time visitor, I want to know where I can find the cafe.
  • As a first-time visitor, I want to know what is on offer.

Returning Visitor Goals

  • As a returning visitor, I want to know if there are any new offers.
  • As a returning visitor, I want to know if there are new items on the menu.

Frequent Visitor Goals

  • As a frequent visitor, I want to know if there is a loyalty/rewards program.
  • As a frequent visitor, I want to know if there are any products I can get to take home.

Target Audience Is:

  • Interested in coffee & bakery treats.
  • Interested in working away from their office.
  • Interested in meeting other people who work from home/away from office.

Features

The website exists on one page with multiple sections and features visible to the user:

Technologies Used

  • HTML was used as the foundation of the webpage.
  • CSS was used to add the styles and layout of the webpage.
  • CSS Flexbox was used to arrange and wrap items on the webpage.
  • JavaScript was used to implement and modify items with the navbar, menu, products, image gallery, and faq.
  • VSCode was used to write and edit code.
  • Git was used as the version control of the webpage.
  • GitHub was used to host the code of the website.

Testing

Compatability

To confirm the website was functional, responsive, and had the correct styling.

  • The webpage was tested on Chrome and Edge browsers, using default dev tools.

    • Chrome:

      A screenshot of the webpage in a maximised Chrome browser A screenshot of the webpage in a shortened width Chrome browser

    • Edge:

      A screenshot of the webpage in a maximised Edge browser. A screenshot of the webpage in a shortened width Edge browser

    • The webpage was also tested using Chrome on a Samsung Galaxy S22+: A screenshot of the webpage in a Chrome browser on a Samsung Galaxy S22+

  • The website's responsiveness was tested using Chrome Developer Tools https://developer.chrome.com/docs/devtools A screenshot of the Chrome Developer Tools A screenshot of the Chrome Developer Tools A screenshot of the Chrome Developer Tools A screenshot of the Chrome Developer Tools

  • The HTML files have passed HTML validity checks with W3C, but had some warnings about sections or articles without headings and info pointers about trailing slashes on self-closing tags. Sections or articles where it did not make sense to have a heading were turned into divs, trailing slashes will be removed before final commit as these are added by default with the formatter that is currently being used. A screenshot of the HTML validation test on W3C for index.html, showing a passed test with no warnings A screenshot of the HTML validation test on W3C for about.html, showing a passed test with info pointers and a warning A screenshot of the HTML validation test on W3C for about.html, showing a passed test with no warnings A screenshot of the HTML validation test on W3C for contact.html, showing a passed test with no warnings A screenshot of the HTML validation test on W3C for menu.html, showing a passed test with info pointers and warnings A screenshot of the HTML validation test on W3C for menu.html, showing a passed test with no warnings A screenshot of the HTML validation test on W3C for products.html, showing a passed test with no warnings

  • The CSS file has passed CSS validity checks with W3C.

    A screenshot of the CSS validation test on W3C, showing a passed test with no warnings

  • The website has been tested for performance, accessibility, best practice, and SEO using https://pagespeed.web.dev/. A screenshot of index.html on PageSpeed Inisghts. Performance: 86, Accessibility: 100, Best Practices: 100, SEO: 91 A screenshot of about.html on PageSpeed Inisghts. Performance: 98, Accessibility: 100, Best Practices: 100, SEO: 91 A screenshot of contact.html on PageSpeed Inisghts. Performance: 89, Accessibility: 100, Best Practices: 78, SEO: 91 A screenshot of contact.html on PageSpeed Inisghts. Performance: 99, Accessibility: 100, Best Practices: 100, SEO: 91 A screenshot of menu.html on PageSpeed Inisghts. Performance: 79, Accessibility: 100, Best Practices: 100, SEO: 90 A screenshot of contact.html on PageSpeed Inisghts. Performance: 36, Accessibility: 95, Best Practices: 100, SEO: 91 A screenshot of contact.html on PageSpeed Inisghts. Performance: 92, Accessibility: 100, Best Practices: 100, SEO: 91

  • The JavaScript files have been tested using https://jshint.com/and have only returned warnings regarding certain functionality being only available in ES6. A screenshot of the jshint

Deployment

Deployment to GitHub Pages

  • The site was deployed to GitHub pages. The steps to deploy are as follows: - In the GitHub repository, navigate to the Settings tab. - From the source section drop-down menu, select the Main Branch, then click "Save". - The page will be automatically refreshed with a detailed ribbon display to indicate the successful deployment.

  • The live link can be found here

Contact

Jamie Heathorn [email protected]

Credits

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published