Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 13 days ago

Responsive layout with Flexbox and custom properties

accessibility, semantic-ui, pure-css
Carlos Alberto da Silva•290
@slayer-br
A solution to the Order summary 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?

'm proud of how closely I matched the design, maintaining semantic structure and responsive behavior with pure HTML and CSS. Next time, I would improve the use of media queries and explore subtle transitions to enhance the user experience.

(pt-BR): Estou orgulhoso de como consegui seguir fielmente o design, mantendo uma estrutura semântica e comportamento responsivo apenas com HTML e CSS. Da próxima vez, eu melhoraria o uso de media queries e exploraria transições sutis para melhorar a experiência do usuário.

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

The main challenge was layering background images with color to match the design. I overcame this by using multiple background layers with background shorthand and testing combinations of linear-gradient and SVGs. I also had some issues with vertical alignment, which were resolved using Flexbox.

(pt-BR): O principal desafio foi sobrepor imagens de fundo com cores para alcançar o visual desejado. Resolvi isso utilizando camadas múltiplas com a propriedade background e testando combinações de linear-gradient e SVGs. Também tive dificuldades com o alinhamento vertical, que resolvi usando Flexbox.

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

I’d appreciate feedback on accessibility best practices, especially for interactive elements like buttons and links. Also, I'm curious if there's a more efficient way to handle responsive background images with pure CSS.

(pt-BR): Gostaria de receber feedback sobre boas práticas de acessibilidade, especialmente para elementos interativos como botões e links. Além disso, tenho curiosidade se existe uma forma mais eficiente de lidar com imagens de fundo responsivas usando apenas CSS.

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 Carlos Alberto da Silva'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
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.