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

Fylo Dark Landing Page using Sass, Parcel, deployed with Netlify

lighthouse, parcel, sass/scss, accessibility
Fluffy Kas•7,675
@FluffyKas
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


Hey guys! I had a blast building this, even if it was a bit challenging at times! It also gave me a good opportunity to experiment with some new tools and I'm kinda happy with how it turned out. I've changed a few small things (on purpose :P).

It would be awesome to get some feedback, especially regarding the HTML. I try to pay attention to semantic markup so I'd love to hear some feedbacks on this (or on anything else really).

edit: When I check on my phone, for some reason it's all messed up, like only half of my css was working. I didn't have this issue with the browser's inspect mode. Can anyone explain me why this may happen?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdulrhman Kotb•395
    @abdo-kotb
    Posted over 3 years ago

    I checked the design on my old phone, and it looks great, so apparently, it has to do with the version or the type of your browser.

    Other than that, your solution looks almost perfect on both desktop and mobile versions, and it helped me figure out an issue with the footer in my solution.

    I only noticed a very minor issue with the productivity-link-holder border on small mobile devices that the border is not exactly the width of the text. You can try using box-shadow, it will make your solution shorter and more efficient.

    Keep up the great work 🔥🔥🔥

    Marked as helpful
  • Benjo Quilario•1,790
    @benjoquilario
    Posted over 3 years ago

    Great job on finishing this one.

    regardless on you problem when css is not working, I also encounter that problem and the problem relies on version of your browser using, because some properties on CSS not working on old version, like gap clamp.

    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