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

Fylo Data Storage Landing Page Using Only HTML And CSS

Raphael Limbikani Mbewe•10
@Raphaelmbewe
A solution to the Fylo data storage component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


please advice me on some improvements that are needed.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Juan Daniel Martínez•500
    @juandadev
    Posted about 5 years ago

    Hello Raphael!

    It was a good try but there are many things you may want to change/improve:

    • To add the fonts to your page, you need to embed the link code from Google Fonts. Just search the correct font and click on it, then select the styles you want no import clicking in the + button, and in the embed tab copy the link tag and paste it on the <head> section near your stylesheets.
    • Fix the call to your fonts, in the font-family property you missed the comma between "Raleway" and sans-serif.
    • Once you correctly link the font, you can change the 185 in the clip div. Instead of putting each number on a separated div, put it together like <div>185</div> or <p>185</p>, the font itself gonna add that style in the numbers.
    • Check the correct colors in the style-guide.md file and try to change it correctly in your containers.
    • The hovers or active states of your project are missing, you can change styles when putting the mouse over an element with selector:hover. It's called a pseudo-class and you can learn more here

    I'm from Mexico, so I still improving my English writing skills, I hope you could understand me 😅.

    You're doing great, keep practicing your CSS skills and happy coding! 🔥

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