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

using html,css(flexbox)

esraagamal•600
@EsraaGamal-22
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Rate my design please, Any feedback and suggestions on how I can improve are very welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shashi Lo•1,345
    @shashilo
    Posted almost 5 years ago

    Hey Esraa. You're getting better at implementing designs, but I do see some areas that you can improve on:

    • The overall container should be max-width: 920px.
    • The method you are using to vertically and horizontally center the project is not ideal. It's not fluid and responsive. I'd remove this and make it margin: auto;. Because you're already using flexbox, add place-items: center;. This will center the elements vertically and horizontally.
    • In the left column, the icon box sizes are inconsistent.
    • Please check the font spacing, white bubble background color, details of the design. There are many little things off about this implementation. Please use PixelPerfect to overlay the design on top of your implementation to view the details I'm talking about.
    • The mobile view is pretty good aside from some padding issues.
    • Look into implementing your CSS mobile first.
  • Jen•1,230
    @En-Jen
    Posted almost 5 years ago

    Hey there, I'd suggest using flexbox instead of floats to position the smaller elements of the design. For example, you could put the two elements with text "0 GB" and "1000 GB" in a flexbox container and then position them using just justify-content: space-between;. Hope that helps!

  • Mohamed Abusrea•160
    @mohamedabusrea
    Posted almost 5 years ago

    Why are you using margin to center the content? try using "align-items" and "justify-content" instead. Also, the design is broken on screens less than 1200px. Try to avoid using fixed values to align items.

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

Oops! 😬

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

Log in with GitHub