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

Fylo-Landing-Page-with-Two-Column-Layout using CSS>Flexbox

RITESH KUMAR•140
@RITESH29-web
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


Hi everyone, I have just completed this challenge using css>flexbox. Any sort of feedback will be helpful. Thanks 😊

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Dave•5,295
    @dwhenson
    Posted over 4 years ago

    hey @RITESH29-web 👋 nice work on this one! Looks great and you've got the design looking really good on desktop views. 🙌 Here's some small suggestions you might like to consider:

    1. At the moment the webpage stretches the full width of the window. This looks a bit strange on large viewports so you probably want to constrain it somehow. I use the approach of setting grid on the body with three columns, and then placing all the direct children in the middle column. You can the adjust the column widths to meet your needs.

    2. At small viewport sizes some of the contents starts to stick out of the page which is causing issues. One issue is the first form - but I think if you but the button inside the form and used flex on the form this would help. It would also help address some of the accessibility issues listed.

    3. The footer layout also looks a bit odd at small sizes. From a quick look I think you have some margin on the ul that you would probably want to adjust. in general, I would suggest doing the mobile layout first, and then adding margin as needed for larger viewports. I find this approach much easier.

    4. Lastly, don't forget that every input element needs a label. I often forget this, but if you don't see a label in the design you can always just include one and then add a visually-hidden class to it to hide it, while keeping available to scree readers. If you google this approach you'll find lots of suggestions and snippets.

    Great work - I really like what you've done with this one and keep it up!! Hope this helps. Cheers 👋

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 4 years ago

    Also a suggestion just to keep it semantic. At your html files, in the form, the button is suppose to submit it right? Well to keep it clear, you could make use of input type of submit instead of just a button right. Also you must include it inside the form tag, because in your markup, it is outside the form, hence when a user interacts with it, nothing will happen since it is not inside of form ^

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