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

First front-end mentor challenge using HTML and CSS

Sophie•75
@0sophietaylor
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first attempt at building a site from scratch on my own - I would love some feedback!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dina•460
    @dinakonto
    Posted over 4 years ago

    Hey Sophie

    Looks great, especially for a first project! Love that you've given all your elements understandable class names, and that you're using a lot of %s for positioning - means you're on your way to responsive code!

    For your next project try playing with another way to position your elements, e.g. Flexbox or CSS grid. Media queries will also take your code to another level - https://www.w3schools.com/css/css_rwd_mediaqueries.asp

    Good luck!

  • Luis Delgado•365
    @luisdevworks
    Posted over 4 years ago

    Hello Sophie,

    Looks great for the fact is the first site built from scratch. I have some issue with the design of the indicator, please check if you can fix that.

    Next time it would be great if you learn some responsive design for small gadgets, I'm pretty sure you will improve a lot your design.

    Good Job!

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