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

HTML, CSS, CSS Variables and Flexbox, Grid and Javascript

P
David Turner•4,130
@brodiewebdt
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my final version of the Easybank challenge. This was my toughest challenge yet. Because of the way I built the main nav I couldn't use border-bottom for the hover state without ruining it. I used a position:absolute "hack" to display the borders so they don't line up perfectly. Any feedback would be appreciated.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    David Turner•4,130
    @brodiewebdt
    Posted over 3 years ago

    At least half of these solutions have been sitting on my computer for a year or more. I couldn't do much because of my family situation. I don't use bootstrap. If I don't feel like styling a site, I will write the html for a site. I have 4 or 5 sites coded and ready to style. I also have components I coded and reuse with some tweaks. I spent a long time trying to code mobile menus, and the one I have now I have used in Sunnyside and Easybank. I am going to use it in the Manage and Bookmark sites. I also have some different footers coded that I use. I have an Accordian that looks like I can use in multiple projects as well. If you find some code you like, save and reuse it. That's what frameworks are.

  • Abdihafid Adan•780
    @Abdul400
    Posted over 3 years ago

    I'd really like to know what your web dev setup looks like. I like how you develop so quickly and they still look so good.

  • Abdihafid Adan•780
    @Abdul400
    Posted over 3 years ago

    I'm not sure how you develop your solutions so rapidly, I see you uploading in quick successions. Do you use bootstrap?

  • Abdihafid Adan•780
    @Abdul400
    Posted over 3 years ago

    I have to admit this looks awesome!!

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.