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

Huddle landing page with single introductory section.

Saurav Chamoli•370
@sauravchamoli17
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


I have used flexbox for the project and developed it in my laptop and it is smaller than the actual desktop design. Constructive criticism is most welcome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Nitya Gulati•665
    @nityagulati
    Posted over 5 years ago

    Hi Saurav, nice work...the site looks good on the laptop. If you want to go a bit further and get the page looking exactly like the design then you can add these few tweaks --

    • Add a box-shadow and hover state for the Register button
    • Currently on the laptop (1220px), the page shows a vertical scroll. To fix that you can resize the image and push the social media and footer sections up to fit everything in single screen frame similar to the design.

    Great job on using flex to switch to mobile layout, however there are some scaling issues at the moment.

    • The mobile design isn't scaled down properly. You'll probably have to go back in your media query and resize the elements to better fit the screen size.

    • Also your current media query for min-width 320px and max-width 480px covers most of the smartphone devices. But I would add couple more breakpoints (as needed) for iPad/tablet devices as well to resize everything accordingly.

    Few breakpoints to consider and test

    min-width: 576px //Bootstrap small device breakpoint (landscape phones)

    min-width: 768px //iPad devices

    min-width: 992px //Bootstrap large device breakpoint (desktops)

    min-width: 1024px //iPad Pro devices

    You can also check out this extensive list of popular device screen sizes

    If you are not using it already, Chrome Developer Tools is a quick and easy way to test and debug different screen breakpoints.

    Good luck! :)

  • omardavidcyber•295
    @omardavidcyber
    Posted over 5 years ago

    The background image is not showing up because you need to change the url location of the image. You have this:

    background: url("/images/bg-desktop.svg");

    Its trying to look for it in the css directory so you need to move up one directory.

    Change it to this:

    background: url("../images/bg-desktop.svg");

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