Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

Huddle landing page with alternating feature blocks

AlexCristea2007•840
@AlexCristea2007
A solution to the Huddle landing page with alternating feature blocks challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm most proud of how I was able to design a clean, responsive landing page with alternating feature blocks that look great on both desktop and mobile devices. The layout works well, and I’m pleased with how the visual design aligns with the overall project goals.

Next time, I would focus on improving the page's performance by optimizing images and assets to reduce loading times. I’d also dedicate more time to cross-browser testing to ensure a consistent experience across all platforms.

What challenges did you encounter, and how did you overcome them?

One of the challenges I encountered was ensuring the landing page was fully responsive across different screen sizes. At first, I had some issues with the layout breaking on smaller devices. To overcome this, I spent more time fine-tuning the CSS, using media queries to adjust the design and ensure it looked good on mobile, tablet, and desktop screens.

Another challenge was optimizing the images and other assets to maintain fast loading times without sacrificing quality. I used image compression tools and carefully selected appropriate formats to balance performance with visual quality.

Through careful testing and iterative improvements, I was able to resolve these issues and deliver a polished, responsive page.

What specific areas of your project would you like help with?

I would appreciate help with optimizing the performance of the landing page. While it’s functioning well, I feel that there may still be room for improvement in terms of loading speed, especially when dealing with images and other assets. I’m also interested in refining the cross-browser compatibility to ensure the design looks consistent across all platforms.

Additionally, any advice on enhancing the user experience, especially with regard to animations or interactions, would be helpful to make the page even more engaging.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on AlexCristea2007's solution.

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.