Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Fylo data storage component

Burcin•120
@burcinalim
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 everyone! I just released my project. I have some questions about evolving my code. I struggled to solve responsive design. When I open the code in Safari, it doesn't work properly. Do you know how I could solve this? Also, some of the elements' spaces are changing when I change the page zoom ratio. (I use Chrome for writing code)

Thank you in advance for any type of suggestions.!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harrismohd93•20
    @Harrismohd93
    Posted over 1 year ago

    See first of all you've included media queries within the CSS classes. This is not the correct way of writing media queries as it will be very much complicated to read and understand. Media queries are usually defined at the end of all Css styles. it's a good practice to write media queries in a logical and organized way, often starting with the smallest screen sizes and gradually moving to larger ones, for easier readability and maintenance. And also the way you have written css is very difficult to maintain,and there is a high chance of missing some brackets or semicolon. As you have missed in box-2 class. I am providing you with a correct way of writing media queries defined with a class name for each breakpoints.

    This is for box-1 class

    .box-1 { width: 100%; height: 15rem; background: var(--Dark-Blue); border-radius: 0.7rem; border-top-right-radius: 7rem; padding: 2rem; }

    .box-1-logo { width: 10rem; margin: 1.5rem 1rem 0; }

    @media (max-width: 400px) { .box-1-logo { width: 7rem; } }

    Likewise box-1 you should make a practice of writing all the css for all the classes once. And then add media queries after writing all the css of all the classes provided in HTML code.

    If you still had any questions,feel free to ask

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