Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Fylo dark theme landing page

accessibility
Fallou Jeng•540
@falloumacbook
A solution to the Fylo dark theme landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, Frontend Mentor Community! 👋

I'm thrilled to announce that I've successfully completed another challenge! 🎉💻

Please check out my solution and provide your valuable feedback.

Thank you for your continued support and encouragement.

Happy coding fellas!!!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Levis Kim•1,230
    @Orekihotarou-k
    Posted over 1 year ago

    Hi there @falloumacbook. Congrats on completing another challenge! 🥳. I took a look at your live solution and there's a few things I think might be of help.

    1. I noticed that you use fixed px values for your widths and heights on the images. I think that using percentage values is easier and also facilitates making them responsive. Here's an example;
    • Create a div for the image in the illustration div and then give the new div (let's call it illustration-image) a width of maybe 80% (this width will always be 80% of the parent container illustration on any screen size).

    .illustration-image { width: 80% }

    • In your style-sheet, select the image inside the illustration-image div and set the width of the image to 100% (this will make the image 100% of it's parent container);

    .illustration-image > img { width: 100% }

    • With this done, you can then change the width of the parent (illustration-image). When you change this value, the size of the image will also be changed as the image is 100% of its parent.

    .illustration-image { width : /* add desired value as a percentage */ }

    1. Using your cards section as an example, I noticed that as the screen gets smaller, the card content just starts to overflow. This is because of the fixed width and height values assigned to them. To fix this, instead of setting fixed values in px, padding can be used to adjust these to your desired sizes. For instance;

    .card { color: white; width: 350px; height: 170px; background: hsl(219, 30%, 18%); margin-bottom: 40px; } these are the styles you applied. Using padding, it'll look something like this;

    .card { color: white; padding: 2rem ; *this sets the padding for top, bottom, left, and right to 2rem* background: hsl(219, 30%, 18%); margin-bottom: 40px; }

    1. Another thing I think may be useful for layouts like this is using grid. Here's a link to help you with that Get started with css grid

    These are just a few things that I think might be helpful as you code along. Happy coding 😊✨

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