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

Responsive landing page using CSS flexbox

Hendrixx•430
@BeeAlmighty
A solution to the QR code component 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 love how i paid attention to structuring my html document to allow ease in implementing CSS Flex-box.

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

Initially, CSS Flexbox was a hassle to implement but i overcame it by applying core fundamental CSS principles as well as good html structure for easy flow.

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

I would like help with

  • Feedback on how close i am to the design.
  • how concise and readable my code is.
  • how structured my html is also. And lastly, alternatives to solve the challenge.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Huy Phan•3,430
    @huyphan2210
    Posted 9 months ago

    Hi, @BeeAlmighty

    I checked out your solution and I have some thoughts:

    • Frontend Mentor will assess your solution once submitted. It's best to review your work and address any potential issues before submitting.
    • Your body doesn't fill the entire viewport. The viewport refers to the visible area of the browser window. To ensure it fills the whole screen, you should apply min-height: 100vh to the body. This is generally considered a best practice for most pages, though there are exceptions. Also, set margin: 0 on the body, make it non-scrollable on desktops, as the browser adds default margins.
    • Since you're using Flexbox on the body, you can easily center the .container (the card) by applying margin: auto. This will center the card within the available space, and Flexbox will handle the rest for you.
    • For better accessibility and readability, try to use more semantic HTML elements instead of relying on divs. Elements like main, footer, and article provide meaning to the structure of the page and are better for SEO and screen readers.
    • You're using h2 for the card title, but there's no h1 on the page. It's better to use h1 for the main heading, as it provides a clear hierarchy for both users and search engines. You can still style it to match the design using CSS.
    • Make your CSS class names more meaningful and descriptive. Research CSS naming conventions like BEM (Block Element Modifier), which can make your code easier to understand and maintain.
    • Lastly, I'd recommend familiarizing yourself with the mobile-first approach. It’s a popular and effective method for building responsive designs, where you start styling for mobile screens and progressively enhance the design for larger screens.

    Hope this helps!

    Marked as helpful
  • Marcelo Meneses•120
    @MenesesMG
    Posted 9 months ago

    Yes

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