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

Skilled e-Learning Landing Page (Vanilla CSS + Easter Egg Hover Card)

Lucas 👾•104,160
@correlucas
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


👾 Hello, Frontend Mentor coding community. This is my solution for the Skilled e-Learning Landing Page!

🤯 The main struggle I had with this challenge was positioning the hero-image overlapping the container. It took 2 days until I get help from Ahmed Bayoumi https://www.frontendmentor.io/profile/Bayoumi-dev that explained me how to create a better html structure and the overflow:hidden; property. I'm really grateful for that!

I added some hover features:

  • 👨‍🔬 Custom hover state on the gradient card using the ~ general sibling combinator .
  • 👻 Custom hover state on card icons.
  • 🎨 custom design improvements: I fixed some box-shadows that were cropped from Figma, If you take a look in the design you'll see that the left shadow from the tablet/mobile image are cropped. I fixed it changing the shadow position on Figma.

🕵 Happy to hear any feedback or advice!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adriano•42,870
    @AdrianoEscarabote
    Posted almost 3 years ago

    Falaa lucas! tudo bem?

    Gostei muito do resultado, observei que você tomou um cuidado com a imagem hero em resoluções maiores e em resoluções menores, o posicionamento dela ficou ótimo!

    Os efeitos que você colocou deu total diferença para a página, mas tenho uma dica:

    Eu abri a página no celular e observei que o padding top da section.hero está um pouco grande, mas nada que tenho um impacto muito grande, só uma opinião mesmo, eu aconselho você a retirar o padding top!

    O resto está perfeito, o prêmio de melhor skilled landing page vai para você!!!

    Tamo junto man!

    Marked as helpful
  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Lucas, this is a really tough one! I remember I was helping someone do some troubleshooting for this challenge, and the positioning of the image was just almost impossible to do. There's still some overlapping of the image and the text at a certain breakpoint, but yes, I think this just really requires a lot of patience to get right, which might be why I haven't done this one yet as my own solution!

    Anyway, I really like what you did in the "popular courses" box (is that the Easter egg? haha!), and the spinning icons are also really cool. As for feedback, the only thing I'd suggest is super minor, and that would be to make the logo a link that links back to the home page, since that is something normally done with a site's logo.

    Great work here as usual, I just love the effort and thought you put into each of your designs. Got lots to learn from you! 😊

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