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

Fylo data component

Lucas Busso•140
@lucasbusso
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Try my best here. Any feedbak for optimization?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Hexer•3,620
    @EmmanuelHexer
    Posted over 3 years ago

    Great work man. But there seems to be only one problem. The "185gb left" is not on the right place.

    Marked as helpful
  • Gareth Carter•235
    @gcarter89
    Posted over 3 years ago

    @Phalcin Good work! Although, I agree with Emmanuel. The 185gb left is not in the right place and is causing some overflow on the right-hand side. This is on a 1440px width screen.

    It looks as though the flex container is making the two left and right containers grow and shrink, while the '185gb left' container is fixed in place. So the problem is that when the screen grows and shrinks, the containers are filling the available space while the '185gb' container stays in place and then overflows the page given its absolute positioning.

    One of the steps I'd suggest is setting the 'R' container to position: 'relative'. This will make the '185gb' container hold its position relative to the 'R' container. You could set the 'top' and 'left' css properties to be relative to the 'R' container, rather than to the nearest 'relative' container which is the body element.

    From there, you can use percentage values on the top/bottom left/right variables to fix the '185gb' container to a position proportional to the 'R' container. Which might help fix it in place.

    I hope this helps!

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

Oops! 😬

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

Log in with GitHub