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

huddle landing page

Isis Daron•40
@isismd
A solution to the Huddle landing page with a single introductory section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello! 👋🏻

I'm still learning and discovering CSS features, any feedback will be appreciated!

If anyone has a suggestion on how to make that main picture looks better in mobile please let me know!😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • JESSE OGBONNA•570
    @JesseOlisa
    Posted over 3 years ago

    Hello @Isis,

    Well Done completing this code. You did an amazing job on this challenge. Keep it up 👍

    I went through your code and I will like to point out the main picture issue. There is no need to set the height of your image at every media query screen.

    My suggestion to making the main picture responsive, and you can do this by adding a display: block and min-width: 100% to the illustration id; With this, the image will always adjust to the width of it's container no matter the screen size.

    I hope this helps😊. Again, Well done.

    Marked as helpful
  • Jorge Miguel•410
    @notFaceroll
    Posted over 3 years ago

    Hey, awesome work on this one. Layout in general looks great!

    On the image issue a suggestion would be:

    • Try setting max-width (usually 100%) instead of max-height and control the actual size of the image by resizing its container. Making it so, in some cases, you won't even need to write more media queries for images :). Generally is easier to work with widths on images. Also, you could set display as 'block' for them;

    and for other topics:

    • You should always have a main element to wrap the main content of the site;
    • Avoid using only (or mostly) IDs as a selector for css. IDs have a higher specificity and since classes can be reused, you would need more IDs or use '!important' to override some styles. This topic https://dev.to/clairecodes/reasons-not-to-use-ids-in-css-4ni4 can pretty much explain this better than me.

    Aside from that, great job on this one!

    Marked as 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