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

Mobile-first e-learning Landing Page using SASS, BEM & CSS Grids

sass/scss, bem
Deborah Robbiano•600
@debriks
A solution to the Skilled e-learning landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi Guys! Another challenge completed! On this one, I got to learn how to resize svg files using the viewBox attribute and a bit more about CSS Grids. As usual, any feedback is welcome! Thank you ✨

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,870
    @AdrianoEscarabote
    Posted over 2 years ago

    Hi Deborah Robbiano, how are you?

    Congratulations on completing another challenge, I really liked the result of your project, but I have a few tips that I think you will like:

    I was having trouble finding a way that at higher resolutions my image would stay fixed while the resolution grew, to fix this I did the following:

    We will create the picture tag that will contain the image, and we will add 3 parent divs around it, I will call it divDad1, divDad2 and so on to make it easier to understand.

    in divDad1 we will put an overflow: hidden;.

    in divDad2 we will put a position: relative;.

    in divDad3 we will put a position: absolute;, and we will position it the way we want.

    Doing this the image will freeze as the screen resolution increases.

    I hope it helps and that it was clear, I'll leave an easier example below... 👍

    <divDad1 style="overflow: hidden;">
        <divDad2 style="position: relative;"
             <divDad3 style="position: absolute; + positioning"
                <picture>
                   <img>
    

    If in doubt, ask!

    the rest is great!

    I finished this project a few days ago, if you want to look, feel free!

    Hope it helps...👍

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