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

Responsive Flyo Landing Page With Two Column Layout

Gabriel Ayuba•270
@Tzienom
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


Hello guys. I just completed the 'Flyo Landing Page With Two Column Layouts'. It was a pretty great experience for me whilst building the project. I had just a few challenges though; here goes:

  1. The link that says 'See how flyo works', what's the best solution to make it underlined all through to the image?

  2. Initially, I made the div container carry the borderline for link and hover state. When it is hovered and the borderline moves up, the rest of the page also moves up. Please, what's the solution to get this done right?

  3. When the CTAs are focused, how do I get it to give user feedback if no email is entered when submit button is pressed?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    👋Hi Gabriel!

    Regarding your questions:

    • What I did to make the underline goes through the image, is by using background-image and width. I set the width: 19ch; to make sure that it will underline the background image. You might want to see my solution on this challenge to understand how it works.
    • Could explain more about your second question, which container are you talking about? There are two containers on your page. Are you still talking about the same link?
    • You can give the alert or error message to the user without any JavaScript. Read this CSS Tricks article.

    Feedback:

    • Accessibility
      • Don't change the root (html) font size. Keep it as default. Changing the root font size, especially using px can cause a lot of issues. Here what an accessibility expert has said about it. Remember that users use different technology and zoom settings to make the text larger or smaller. Changing root font size can break all sorts for them.
      • You don't need to put the word logo on the alternative text. The user who uses screen reader already know that it is a logo the same as we see the Fylo image. Another reason for it, since you have already used the img tag, the screen reader will automatically tell that it is an image 😉.
      • For any decorative images, each img tag should have empty alt="" and aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images. In this case, all illustration images, phone and email icons are decorative only.
      • You might want to read this article from W3C WAI about images.
      • I would recommend wrapping each section inside the main tag with section tag for more semantic markup.
      • Wrap the input and the button with a form tag and also add type="submit" to the button, since if this is a "real website" then it will submit the user email.
    • Other
      • This chunk of HTML code should be lived inside the main landmark, since this is a hero section or similar like that.
     <div class="header-text">
                    <h1>
                        All your files in one secure location, accessible
                        anywhere.
                    </h1>
                    <p>
                        Flyo stores your most important files in one secure location.
                        Access them wherever you need, share and collaborate with friends,
                        family, and co-workers.
                    </p>
    
                    <div class="header-cta">
                        <input type="email" name="email" placeholder="Enter your email...">
                    </div>
                    
                    <div class="header-button">
                        <button>Get Started</button>
                    </div>
                
                </div>
    
                <div class="header-image container">
                    <img src="images/illustration-1.svg" alt="illustration-1">
                </div>
    

    That's it! Hopefully, this is helpful!

    Marked as helpful
  • Gabriel Ayuba•270
    @Tzienom
    Posted about 3 years ago

    Hey, sir. I was away for a pretty long time, but I'm grateful for your feedback. It was helpful.

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