Skip to content

Latest commit

 

History

History
53 lines (30 loc) · 2.64 KB

README.md

File metadata and controls

53 lines (30 loc) · 2.64 KB
Raw

Base Apparel coming soon page

Solution : Live Site URL

Solution submitted at Frontend Mentor - Submission link

This is a solution to the Base Apparel coming soon page challenge on Frontend Mentor.

Design preview for the Base Apparel coming soon page coding challenge

The challenge

Your challenge is to build out this coming soon page and get it looking as close to the design as possible.

You can use any tools you like to help you complete the challenge. So if you've got something you'd like to practice, feel free to give it a go.

Your users should be able to:

  • View the optimal layout for the site depending on their device's screen size
  • See hover states for all interactive elements on the page
  • Receive an error message when the form is submitted if:
    • The input field is empty
    • The email address is not formatted correctly

###Built with

  • HTML
  • CSS
  • CSS Flexbox
  • JavaScript

Experience & Challenges

The layout was a little difficult to understand as in the desktop view the image takes the right side of the page but in the mobile view the hero mobile image is different and is between the logo and the main content. This would have been easy with grid but the logo area and the main content area share a common background image and background color gradient which meant the hero image would have to be on top of the these grids but grid elements don't collapse on each other. So that made me re-think the layout structure.

At the end I used flexbox, two separate hero images each only visible in the expected screen sizes.

For form validation I used a combination of HTML5 validation and JS taking advantage of the browser's Constraint Validation API which consists of set methods and properties available on form elements DOM interfaces.

Continued development & Learning

I learned some more ways of using CSS animations.

I learned about various ways to do form validation and eventually implemented form validation using the browser's Constraint Validation API. Read more about it at MDN

Accessibility wise I am no happy with the way I designed the form elements and hiding outline is not the way to go so will read up more about accessibility options for form elements and try to fix it.

Pending Tasks
  • Final challenge screenshot(s) (desktop and mobile)