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

Fylo dark theme landing page CSS Grid and Flexbox

hammercait•250
@hammercait
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


I had a bit of trouble with positioning the background image so any guidance on that (or any other constructive thoughts) are more than welcome!

Media queries are foreign to me so this one doesn't have one yet. If anyone has guidance on sizing for different screens I would VERY much appreciate it! :)

Updated to do media queries 9/14.
Any feedback still welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mark Mitchell•1,820
    @markup-mitchell
    Posted almost 5 years ago

    Hi @hammercait! I think media queries are one of those things that seems totally baffling... until the penny drops and then you wonder why you found it so hard (like every new coding concept 😅). I struggled with them, and even now I only use them in a very minimal way.

    You can think of them as conditional statements for CSS:

    @media (min-width: 768px) { body { background-color: red; }; }

    means "if (viewport is 768px or more) then apply style (body { background: red})"

    I suggest you only use min-width until you really need something else (I rarely do).

    This goes hand-in-hand with the "mobile first" approach because it's easier/better, for various reasons, to implement mobile-friendly designs first, then expand them to work on tablet and desktop.

    Try starting your next challenge with the mobile design: develop it in devtools with the device emulator set to iPhone6/7/8 (or 375px). When the mobile version is finished you can start adding media queries to realise the desktop (or tablet) design.

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.

Oops! 😬

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

Log in with GitHub