• Overview
  • Intro
  • The challenge
  • Links
• My process
  • Built with
  • Features
  • Useful resources

Hello! This is my solution to Easybank landing page - Frontend Mentor. That was a relatively simple challenge but still there was a room to try some new things and learn new approaches. The hardest thing to do was setting these mockups backgrounds and to fit it with design.

Your challenge is to build out this landing 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.

The only JavaScript required is for the mobile navigation toggle. However, you could also try doing this without JS.

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

• LIVE PREVIEW to check my solution.
• Frontend Mentor challenges allow you to improve your skills in a real-life workflow.

• Webpack
• SCSS
• BEM methodology
• Mobile first
• Semantic HTML5 markup
• JavaScript
• Flexbox
• Grid
• Intersection Observer API

• Added touch-enabled mobile navigation. It's hard to reach for the hamburger menu on larger phones so I added a menu that is enabled by touchmove feature. Swipe from left to right to open menu on mobiles.
• Implemented Skip to content link. Skip links are little internal navigation links that help users move around a page. It is used as an accessibility enhancement that lets keyboard users and screen readers jump from the top of the page to the content without have to go through other elements on the page first.
• Applied load events to prevent animating content before assets has downloaded. In short it is using JavaScript to listen for a load event, and make use animation-play-state to pause our animations until the assets has downloaded. This one I found in Anna solution, so special thanks to her.
• Instead of repeat code for reusable elements i write some helper classes to reuse them throughout the project. I created classes for headings, paragraphs, container. This saves time as well as unnecessary code repetition. I will definitely try to improve in this aspect.
• Added sticky nav menu using Intersection Observer API. In short, this API is a native way of detecting if an object has entered the viewport. My observer looking at .kv section, and if that section is no longer interacting with viewport it triggers my header to appear.
• I used Sass at-rules @for which is a simple for loop to transition my header__nav-item's while my mobile menu is open.
• Implemented prefers-reduced-motion CSS media feature which is used to detect if the user has requested that the system minimize the amount of non-essential motion it uses. Prevent animations in brief.
• :focus-visible pseudo class. This selector only indicate focus when it is helpful to the user - such as in cases where the user interacts with the page via a keyboard or some other non-pointing device. It isn't supported by Safari yet, but there is simple workaround.
• Tried to create more accessible mobile navigation. Used the aria-expanded and aria-controls attributes.
• To create this project I used webpack. More specifically i used laravel mix which is a wrapper for webpack and targets the 80% usecase.

• LINK - touch-events
• LINK - skip-to-content link
• LINK - load-events
• DOCS - Intersection Observer
• DOCS - Sass @for
• LINK - webpack