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

Huddle Landing Page with pure css

INexplicableName•40
@TheLiberal
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


This time I had trouble with the mockup image as I didn't know wheter it should be put in a container representing the left part of the bigger flex container or just sitting there alone. I settled with the latter, which later presented a problem with widths of 1100px+ until a certain point. If anyone could explain that to me and give me any tips regarding anything that's still wrong about this implementation, I'd be very grateful. Also I made the same mistake as the last time, because I styled some element/s using IDs and now I know that I shouldn't.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roman Filenko•3,335
    @rfilenko
    Posted almost 5 years ago

    Hi Błażej, good job, but with a few corrections can be a lot better. I was wondering about choices you made, so here a few tips for improvement:

    • please don't use !important, id's you already mentioned;
    • add max-width to .container and center it;
    • fix img distorted proportions(max-width: 100% for all imgs, object-fit:contain as option for big one image);
    • why social icons have absolute position?
    • what the purpose of address in footer? Hope this was helpful feedback for you, have a good day.

    Keep practicing, Roman

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted almost 5 years ago

    Hey, Błażej Gułaj! 👋

    Nice work on this challenge! 👍

    I suggest,

    • Decreasing the space between the hero image and the text on the left side of the screen.
    • Making sure that the image scales (not stretches) when the page is resized (you should be able to do this by setting either one of the width or height properties to auto).
    • An idea for how to place the image would be two create two containers (both of which take up 50% of the available width of their parent container) put the image in the left container and make sure it fills up 80-100% of that container's width and put the text in the right container like you've done.

    Keep coding (and happy coding, too)! 😁

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub