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

Responsive QR Code Component Page Using Tailwind

accessibility, tailwind-css, web-components
codewthv•60
@codewthv
A solution to the Space tourism multi-page website 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 using Tailwind CSS for the first time on an actual project. It was exciting to explore utility-first styling, and it helped me write cleaner and more structured HTML without relying on a separate CSS file.

Next time, I plan to make the component fully responsive using Tailwind's built-in responsive classes, rather than writing traditional media queries. This will help me practice using Tailwind breakpoints and build more scalable designs.

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

The main challenge I faced was maneuvering my way through Tailwind CSS. Since I was new to the utility-first approach, it took some time to understand how to translate traditional CSS techniques into Tailwind classes.

I overcame this by:

  • Frequently referring to the Tailwind CSS documentation

  • Looking at code examples from the Frontend Mentor community

  • Breaking down each UI section and styling it step-by-step with Tailwind utilities

What specific areas of your project would you like help with?
  • Make a site fully responsive using Tailwind CSS breakpoints (e.g., sm:, md:, lg:)

  • Create a better layout structure that adapts cleanly across different screen sizes

  • Improve accessibility and semantics while using Tailwind classes

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 codewthv'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

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.