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

Centered card layout using Flexbox

Sreejith c s•20
@sreejithcs007
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'm proud of how clean and responsive the layout turned out using only HTML and CSS. I managed to center the card perfectly on the page using Flexbox and styled the elements to match the design spec closely. I also maintained a clean, organized structure in my code with meaningful class names and a mobile-first approach.

This project helped me get more comfortable with layout techniques and responsive design.

I'd also consider implementing dark mode support or adding a small animation to make the UI feel more interactive.

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

At first, centering the card both vertically and horizontally was tricky. I tried using margins but it didn’t work consistently across screen sizes. ✅ Solution: I used Flexbox on the body to center the .inner_container perfectly, even on small screens.

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

I’d love feedback on whether my CSS structure and class naming follow best practices. Are there ways I can make my styles more modular or maintainable?

While the layout looks good on mobile and desktop, I’d appreciate suggestions on how I could make the design even more responsive, or if there are better techniques I could use.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    joaoc-dev•50
    @joaoc-dev
    Posted 3 months ago

    Great work!

    I would look into semantic html as a way to possibly improve your html structure: HTML Semantic Elements

    I would also avoid generic css class names like .para_1 and .para_2

    Regarding naming conventions, you can look into BEM for future more complex projects: CSS BEM methodology

    Marked as helpful
  • P
    JESUS ANGUIANO•140
    @AnguiNator
    Posted 3 months ago

    Cambios recomendados: ✅ Renombrar clases usando la metodología BEM.

    ✅ Usar variables CSS para colores y espacios comunes.

    ✅ Arreglar el color mal escrito (color: 1F314F; → #1F314F).

  • Zaia•10
    @zyre-mendoza
    Posted 3 months ago

    I think you already get the concept---just make sure to follow the correct spacing, margin, and padding. Follow the design :>

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

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