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

Fylo component using Sass & flexbox - Desktop first

Jen•1,230
@En-Jen
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Don't have any questions in particular but any feedback is welcome as I am still a beginner coder. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dorian Alvarado•240
    @Dorian30
    Posted almost 5 years ago

    Really interesting Jen! I like this solution. I came here, after you submitted your feedback on my solution. I really liked yours! After reading your feedback I thought I could come and learn some things. From my side I have only a few quick notes.

    I would suggest to use more semantic tags for your HTML. Also, for illustrative images like the wave below the page I think it is better to use pseudo elements ::after or ::before and avoid making your HTML more verbose.

    On a side note, I would like to ask you why choosing rem as your first option. I really like how you kept consistency and only used rem, but why choosing that above the others ?

    Also, I saw that in your HTML you wrote font-size: 67% (or some value near that one, I don't remember), but different browsers can have different font sizes. Here I think we are assuming we will have 16px across every browser, or was this intentional ? In that case, what are the reasons for doing that ? Isn't it better to sent a default font size to reset browsers fonts ?

    Looking forward to your answer!

  • Freddy Munive•170
    @fmunives
    Posted almost 5 years ago

    Hi Jen,

    You had a great job and your styles are very ordered. You're using BEM, that's a good methodologie to work.

    The unique recomendation when you declared transition: all .3s; and later you give the &:hover { border: 1px solid $color-file-icon; }

    For performance it's better to be more specific with the value because all applies for all properties and you just need to apply border property.

    You can check your code in 38 line https://github.com/En-Jen/fm-fylo-data-storage-component/blob/master/sass/components/_files.scss

  • Matt Studdert•13,611
    @mattstuddert
    Posted almost 5 years ago

    Hey Jen, I've only just come across this solution. I don't have much to add beyond the great tips that have already been given. So I'll just say, amazing work! Your solution looks great and scales down really well to mobile.

    You mentioned in the title that you went desktop first. Is that a personal preference? Even if you didn't work mobile-first I'd still recommend using min-width media queries. It can often lead to less CSS code and has the benefit of loading in fewer styles for mobile users, which can be a nice performance gain.

    Keep up the awesome work! 👍

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub