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

Responsive Component, Flexbox, Grid, skeumorphism design.

tailwind-css
Luis Rosas•40
@LuiRo07
A solution to the Results 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?

I'm proud of the continue button that hovers with a color that matches the aesthetic and feel of the component. I would take a mobile-first approach next time, and use more complex technologies like React to build a reusable component that could be implemented in future projects.

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

The container that holds the results and summary data needed to have dimensions that needs to be split in half, to share between both, so I needed to make one big component in this case the summary, and the results container needs to be half the size and sit next to each other. I used flexbox for that, and using its default flex-direction property allowed me to do just that. This way it can also add responsiveness to the component to switch from row to column for its flex-direction property in a smaller screen.

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

I would like some tips and advice for building responsive components that look good on all devices. My component looks good on small devices with large screen but not smaller screens. The user needs to scroll down to view the "Continue" button.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Luis Rosas'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 1st-party linked stylesheets, and styles within <style> tags.

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.