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

Responsive scan card using flex-box (Tailwind-CSS)

next, tailwind-css
danielmututa•10
@danielmututa
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?

Pleasant afternoon! My name is Daniel, and I'm a frontend developer from Harare, Zimbabwe, with 6 months of experience. Recently, I built a project called Scan-project, which allows users to scan their projects and generate a unique URL. I'm most proud of how I was able to bring this idea to life using Next.js and Tailwind CSS for the first time. The project challenged me to learn new technologies and apply them effectively, especially with responsive design and font management.

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

One challenge I faced was importing images and getting comfortable with Tailwind CSS. Initially, I struggled to understand how to import images properly in Next.js, but I overcame this by watching a helpful tutorial on YouTube. For Tailwind CSS, I ran into some difficulties applying styles effectively, so I turned to the official Tailwind CSS documentation, which provided clear examples and solutions. These resources made a huge difference, and I’m now more confident troubleshooting and using Tailwind CSS in my projects.

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

I am looking for guidance on new projects that can help me advance my skills, particularly with Next.js. In my recent project, I did not work with routes, and now I am eager to dive deeper into routing in Next.js. Specifically, I would like to better understand dynamic routing, nested routes, and URL parameters.

Could anyone recommend tutorials, resources, or projects that emphasize these concepts? Additionally, if there are any best practices or common pitfalls related to routing in Next.js, I would love to hear about them.

I am excited to continue building my knowledge and refining my skills in real-world applications. Any help would be greatly appreciated!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Samuel Lwanga•50
    @babyanonymouse
    Posted 7 months ago

    the code's nice, although the other "scan...." text is slightly gray on the design

    Marked as helpful

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub