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

Fylo-data-storage-component HTML/CSS

Artem Ponomarenko•365
@ArtemPonomarenko
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello guys,

At first it seems like a very simple project, but it has few tricky bits. Progress bar is quite hard to customise. And background keeps sliding sideways on the mobile version. It was quite a challenge =)

Is there a way to test your mobile solution against the design? The same way I check it for the desktop version, with vertical line?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Anna Leigh•5,135
    @brasspetals
    Posted almost 5 years ago

    Hi Artem!

    I spent hours trying to get both a progress and meter bar to style correctly. Right now, I simply do not think it is possible to style either perfectly and also have that style be cross-browser compatible. I asked about it in my own solution and got no answers. The only way I've found to create that bar and have it actually follow the design (white dot and all) is just using divs. Hopefully in the future, styling for progress elements will be better supported. Huge kudos for trying.

    I'm also seconding Em's comments on the background. There's an alternate background specifically for mobile, which you can switch to with a media query.

    Overall though, good job! 👏

  • Emmilie Estabillo•5,600
    @emestabillo
    Posted almost 5 years ago

    Hey Artem, great job! Interesting styling of the progress bar, putting it on the value attribute. I would double check the colors on the style guide though, it looks a little off. Note: The screenshot didn't seem to take it. I also tested on Firefox and it's the result is the same blue bar.

    For your background, you are using the desktop version for mobile screens. You can probably remove background positioning after adjusting this. Also, you can simply put the background in body instead of creating another div. Not sure what you meant about testing in mobile, but it's mostly the same by using dev tools and either adjusting your screen width or using the toggle device toolbar. Hope this helps!

  • Roman Filenko•3,335
    @rfilenko
    Posted almost 5 years ago

    Hi Artem, great work on this one. As for screenshot - it probably because puppeteer (would guess in this case) creates screenshot before yor styles kickoff. Have a few notes though:

    • tags could be more semantic;
    • progressbar is rather hard to style, add vendor prefixes to make it crossbrowser;
    • some strange values like height: 201px; width: 918px; margin-bottom: 34.2px; - a bit lack of consistency here, but you probably used all values from sketch file;

    Cheers, Roman

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted almost 5 years ago

    Wow! You have so much good feedback already, Artem! 😄

    • Perhaps turning the option icons into actual links and giving them a hover state might be a nice extra touch. Just a suggestion!

    I'll just say good work and keep coding (and happy coding, too, of course)! 😉

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

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

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