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

Mobile-first webpage built with HTML, Sass, and JS

Rabin Gharti Magar•455
@Rabin92
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have finally completed this challenge!!

I found the hero section very challenging however I somehow managed to fix it by doing some research and watching a few tutorials. This challenge really tested out my layout skills and I am very glad that I got to learn new techniques and acquire new knowledge which I was not aware of.

Any feedback regarding my solution and my code would be greatly appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tesla_Ambassador•3,070
    @tesla-ambassador
    Posted over 4 years ago

    I really like what you did with this challenge my favorite bit is the way you used the opacity on the pictures in the "Latest Article" section

  • P
    The Burrito Doggie•1,260
    @BurritoDoggie
    Posted over 4 years ago

    hello Rabin Gharti Magar,

    I really think it is fantastic. It actually looks like it would be from Github. I can't really correct you on anything since I am definitely not as good as you. I just wanted to say that it is really cool.

    Keep Coding!

                                         (@@)
                                          \__/
    
  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Hi, Rabin Gharti Magar! 👋

    Well done on this challenge! 👍 Your solution looks great and responds very well! 👏

    A tiny thing I might suggest is replacing the hamburger menu icon with an "X" icon when the menu is open. I think might be a nice extra touch! 😉

    Keep coding (and happy coding, too)! 😁

  • brigittavarga•55
    @brigittavarga
    Posted over 4 years ago

    Nice job on this one, looks great! I am currently working on this challenge, going to add extra pages to it for practice with my designs. Going to share the result soon!

  • Anna Leigh•5,135
    @brasspetals
    Posted over 4 years ago

    Hi, Rabin! 👋

    Excellent job on this solution! 🎉 It responds very well, and looks great on large screens (1920px) too! Your work on the hero images paid off. What were the new techniques you learned on this project?

    You really did a good job here, and I could only find a few, small suggestions:

    • Adding object-fit: cover to your .article__image will allow the image to fill the height and width while maintaining its original aspect ratio - right now the images can get a little bit distorted.
    • You might change the footer layout switch to a little later/wider. At around 685px it feels very squished.

    Happy coding!

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
Frontend Mentor logo

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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

Oops! 😬

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

Log in with GitHub