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

Fully Responsive Page on All Devices Using Boostrap 5 and CSS

MUHAMMAD NOMAN WALEED•10
@NomanWaleed
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


Hi Community! I have completed this challenge but I had to use too many CSS media queries to make it responsive on all devices. I used Bootstrap 5 too but didn't fix the issues all the time. Kindly have a look at the code and suggest to me what can I improve. Thanks.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • hardy•3,640
    @hardy333
    Posted almost 4 years ago

    hey, website looks good. nice job.

    Few suggestions:

    • try to align huddle logo and big showcase image correctly on left size, for that I suggest you to use one container/wrapper div which will have some margin from left, your logo and image will be exactly the left side of that container.

    • Try to add box shadow on cta button and maybe some more hover effects on it...

    • In terms of using bootstrap, it is ok but you don't need bootstrap here, it will make your life just harder, this is very simple layout use instead vanilla css ...

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

    Hey, great work on this. Layout looks good both desktop and mobile. The responsiveness is fine as well.

    I second to what hardy said about bootstrap. You don't need that in here. Go with just pure vanilla css or scss. That would make you much greater in stylings, do not go using framework.

    Some other suggestions would be:

    • The alt text for the website logo should be alt="huddle". The website logo already have the text on it, better use it as the alt value.
    • Always have a main element on a webpage. This helps user navigate properly within your site. On this, the div that captures all the layout should be the main tag.
    • The register should use a tag instead of button.
    • The register lacks a visual indicator on it. If you try using tab key in your keyboard, you won't see anything that indicates you are within the element. Use some stylings in the :focus-visible selector of that element. Apllying a outline or border or box-shadow.
    • The social media links should be inside ul element, each with their own li element, since those are list of links.
    • The a tag that wrap the social media link should have aria-label on it. For example:
    <a aria-label="facebook">
      { the icon in here }
    </a>
    

    This way, users will know where this link will take them.

    Aside from those, great work.

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

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