Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Easybank Landing Page featuring HTML, SASS and Javascript.

Khael•230
@i-am-Khael
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Everyone's feedback is always appreciated..

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fluffy Kas•7,655
    @FluffyKas
    Posted over 3 years ago

    Heyo,

    It looks pretty good on mobile and desktop screens. I feel like the sizes in between could be a bit smoother (you could adjust the media query a bit to switch at a different size or perhaps add different queries for the different sections). There are some other issues, smaller and bigger as well you may want to look into:

    1. Regarding your Sass/css: it feels like you're abusing nesting a bit which makes your code really hard to read. For example: if you name your module "footer.scss" I think it's somewhat unnecessary to nest every single element inside footer in the file itself. You'll end up with a bunch of }}} in your code that is hard to sort out. You're also following some strange practices to target elements: "div.header-intro-paragraph", "img.bg-intro-desktop". I don't really see the reason why you combine element selectors with class selectors. Class selectors in themselves should be specific enough, combining the two seems confusing. If you have any reason to do things this way, please let me know because I'm really curious!

    2. Your nav links should be wrapped in <li>s and contained by a <ul> instead of a div. I'm also not sure how good of a practice it is to have a separate desktop and mobile menu in your markup.

    3. Your buttons are using the browser's default font, so their font-family need to be overwritten ^^

    4. I suggest reading this article, it helps a lot to understand what alt texts are for and how to write useful ones.

    5. In the Why Choose Easybank sections, your labels should be swapped with headings. Labels are for labeling form elements, like inputs, checkboxes, textareas, etc.

    6. Article section: You could swap these divs with articles, it's the perfect use case for the <article> element. Instead labels, use headings here too!

    7. Social links: instead of alt texts, aria-labels would be perhaps a better choice! They could also be wrapped in <ul>, just like your nav links. Same goes for the other footer links!

    Sorry for the wall of text, I hope it was somewhat useful at least >.< All in all, I think you did good on a really tough challenge! It's just the markup and clean coding practices that you might want to work on a bit. Good luck!

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub