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

Responsive landing page using HTML and CSS

Eder Procopio•30
@EderProcopio
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


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

This was my first solo project using CSS Grid. Although it was simple, positioning the items took quite a bit of work. As it was my first time using Grid, it was also my first time implementing a mobile-first approach. To be honest, I prefer desktop-first. I chose these approaches to challenge my knowledge, and as a bonus, I got to test my problem-solving skills.

I prioritized responsiveness in the design, and because of that, I sacrificed some similarity to the original challenge. The page’s active state works very well, and all the social media icons are functional. I tried to replace the Twitter icon with the new X icon, but by the time I finished the challenge, the link to the X icon on FontAwesome.com wasn’t working.

If I had to redo the project, I wouldn’t use percentage-based dimensions for the images. While this approach adapts to various screen sizes, it distorts the page's final layout.

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

Positioning the elements was the most challenging part, especially in the desktop design where I used CSS Grid. Additionally, I felt that I could have structured the HTML code better, which would have saved me from some unnecessary headaches.

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

I'm starting to learn programming, mostly in a self-taught way, because although I'm taking an online course, it's not the same as having tutors and friends to ask questions. I haven’t gotten my first job as a developer yet, so my main challenge is learning how to structure code according to best development practices. I also often feel unsure about whether my design looks professional enough.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yamien Ariel•210
    @ariel172
    Posted 8 months ago

    Wow! I'm impressed, your solution is great!

    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