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

Mobile first responsive site using HTML, CSS, animations, and SASS 😀

P
Isaac Novaesâ€ĸ650
@isaacnovaes
A solution to the Fylo dark theme landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Besides completing the challenge, I took the initiative to add not only a few animations, but also an external page, which is the destination to all available site links.

I challenge you to find a mistake 😏 More than that! I challenge you to find a mistake and leave a comment 😎

Kidding aside, I really appreciate every feedback. Thanks in advance! 😀

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Isaac Novaesâ€ĸ650
    @isaacnovaes
    Posted about 4 years ago

    Hello, Juan!

    First of all, I appreciate your feedback. Thank you man.

    Second of all, I am afraid that I will increase the empty space among the testimonials, because the testimonial container will exceed the global frame of the site, i.e. this increase will break the global pattern margin of the site. In addition, I will increase the vertical space among the sections because I totally agree with you in this point.

    Well, thank you once again 😀

  • John Rey Faciolanâ€ĸ220
    @juani2
    Posted about 4 years ago

    Hello Isaac,

    Great Work! I love the smooth animation on the form!

    By the way, you might also try to increase the white space of your major page sections and inside the testimonial cards.

    That way, There will be more breathing room for your page elements giving it an improve reading experience.

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

Oops! đŸ˜Ŧ

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

Log in with GitHub