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

HTML Sass Vanilla JavaScript Vs Code

Roc Tanweer•2,500
@RocTanweer
A solution to the Digital bank landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello there,

Any learner who wish to learn and guide may see a brief note here of making this site.

Anywhere you see 'rem()' function, it's a function made in _variables.scss in Sass folder to convert pixels into rems. And there is also a mixin named responsiveness to handle media queries in an awesome way!

Any feedback is appreciated!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hi, RocTanweer! 👋

    • The layouts at specific media queries look great, and you’ve clearly put in a lot of thought into them. Ideally, however, your solution would look good on all screen sizes, not just a handful of set widths. I would suggest in future projects to focus on responsive design. I see you’ve used a bit of Flexbox, which is great! I encourage you to dig deeper into it, as it’s great for responsiveness. Grid is also really good, but I’d learn one at a time as to not get yourself too confused in the process. Here’s a really nice resource for Flexbox that also has some great links at the bottom of it. For image responsiveness, I’ve found a width percentage combined with a max-width usually works pretty well. The object-fit property can also be really useful. There’s also picture and figure elements, although I still have a lot of learning to do about those myself. 😄

    • Another great resource is this admittedly long article on semantic html. I refer back to often, and I’ve found it really helpful for my projects.

    • For the errors in your report, adding title tags inside the svg of your social icons should clear them up. Here’s an example:

    <a href=“#”
          <svg…
            <title>instagram</title>
             <path>…
    

    I realize this feedback isn’t picking out specific elements, but I hope it’s still helpful! Happy coding!

  • Moses•65
    @consolexyz
    Posted over 4 years ago

    The mocks up is not positioned well oj Mobile devices 375px

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 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

Oops! 😬

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

Log in with GitHub