Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Responsive Fylo using HTML, SCSS, & JavaScript

accessibility, bem, sass/scss
Rebecca Padgett•2,100
@bccpadge
A solution to the Fylo landing page with two column layout challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

The only thing I would do differently, is use React and Tailwind CSS.

What challenges did you encounter, and how did you overcome them?

N/A

What specific areas of your project would you like help with?

All feedback is welcome and greatly appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Nishanth Venkatesan•1,030
    @nishanth1596
    Posted about 1 month ago

    Hi Rebecca! Excellent work on this challenge! 🎉 It’s really impressive how semantic and accessible your HTML is! The transitions and animations look super smooth, Im definitely going to steal a few of these ideas for my next challenge 😉

    My few suggestions are; 1.Decorative Image Optimization Since the illustration is decorative, you can simplify the markup by removing the <figcaption> and aria-hidden="true". An empty alt attribute (alt="") is enough to hide it from screen readers

      <figure class="productive__banner">
              <img class="intro__img" src="./assets/images/illustration-2.svg" alt="" aria-hidden="true">
              <figcaption class="visually-hidden">Image doesn't need a caption</figcaption>
            </figure>
    
    
    <figure class="productive__banner">
              <img class="intro__img" src="./assets/images/illustration-2.svg" alt="" >
    </figure>
    

    2.Improving Tablet Layout UX For tablet screens, consider adding more horizontal padding and constraining the width of the input and button fields. Centering them would improve the overall visual balance. This is also where using React (or any component-based UI library) could shine, you only need to update the button/input styles once, and it would reflect everywhere!

    Again, great job! Keep up the amazing work and keep pushing yourself with more advanced setups like React, you’re clearly ready for it! 🚀

    Marked as helpful
  • Marzia Jalili•7,070
    @MarziaJalili
    Posted about 1 month ago

    That's an A game build, no cap! 👑

    A tiny suggestion?

    For a lengthy home page, it's best practice to have a to top button. A button that shows up all across the page and when clicked will take users to the top of the page.

    ✅ As if the href attribute is set to # in the <a> element, it gets this job done so we will use that.

    ✅ And to make sure that the link appear all across the page, set its position to fixed. This won't affect other element too.

    ✅ You could take the example below into account:

    <a href="#" className="top-btn">Top</a>
    
    .top-btn {
      position: fixed;
      z-index: 100;
    }
    

    ✅ Or you could have it set as the one in the footer.

    Other than that, the web’s lit!

    🔥🔥🔥

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