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

Landing Page

Roderick Hollingsworth•35
@rhollings
A solution to the Agency landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Trouble making it responsive. Not sure if I should how to go about making it best for mobile and web. On mobile the client section and the footer overlap. Some images have white space between them, not sure how. Open to all suggestions. In the end, it was a fun project to test my skills and level. Definitely not done learning

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdullah Nassif•405
    @AbNassif
    Posted almost 4 years ago

    First of all, really love your attitude towards knowing you made mistakes. We all do, and they are essential in making us the best at what we do.

    1- Love that you took the initiative in making the navbar fixed to the top as someone is scrolling. But I can't see the links once I've scrolled, so consider adding a darker background once a scroll is initiated. (Google ways you can do that, but I think you most probably need javascript for that)

    2-The nav bar isn't responsive because you added padding of 45rem to the right for the li.left-nav. That is a big no-no in the css standards, as it won't scale well on any other device other than one's similar to your screen.

    To fixed that, remove the logo from the ul all together and add it to a separate div.tag (It should be the ul's sibling instead of it's child). Then a super easy way would be to add another div tag in between the logo and links and give it a margin of auto. That way it'll take up the whole space of the nav bar and align them perfectly across all screens.

    (There are plenty of other ways, but this is the easiest of them all)

    3-Always and always fix the responsivity of the section before creating another one, I did that once and it ended really badly for the project I was working on. Learn media queries and read about responsive units(Vh,VW,%) and how you can use them to reduce the code required for mobile responsiveness.

    4- To fix the orange missing as the viewport changes, just change the "background-position" property to "bottom" in media query.

    5- You forgot to add the milk image above the footer. Just add a display of flex, then give all of them a specified width to fit the viewport, and add flex-wrap to break the down vertically as the viewport get's smaller. You could then use media queries to increase their width as each image get less competition for the row it's in.

    Honestly couldn't figure out the reason behind the whitespace between the images in the center, and why they're taking 150% of the screen size(having to scroll horizontally), But It's so messy and it would be counterproductive to spend your time fixing it now. So just pat yourself on the back as this challenge isn't as easy as it seems, and remember to break everything down next time and make sure that each part is mobile responsive before moving on to building the next part.

    Great job!

    Marked as helpful
  • Account deletedPosted almost 4 years ago

    The picture with the orange is missing on desktop, it like literally disappears.

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