Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Responsive webpage with html5, tailwindcss

tailwind-css
ERNEST ANOKYE•80
@iamernesto14
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?

Reflecting on my recent QR code webpage project using HTML and TailwindCSS, I'm proud of achieving a clean, responsive design. TailwindCSS's utility-first approach made styling efficient and modular, speeding up development and keeping the codebase organized. This project solidified my understanding of responsive web design and TailwindCSS.

Looking ahead, I see areas for improvement. I plan to enhance accessibility by adding aria-labels and ensuring proper color contrast. Breaking down components further will boost reusability and maintainability. Additionally, optimizing images and assets for faster page loads will improve user experience. These lessons will guide my future projects, ensuring they are more inclusive, efficient, and high-performing.

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

During my QR code webpage project, I encountered several challenges that required thoughtful solutions.

One major challenge was ensuring the design was fully responsive across various screen sizes. TailwindCSS’s utility classes needed some tweaking to achieve the desired layout. I extensively used TailwindCSS’s responsive utilities and tested the design on different screen sizes using browser developer tools and real devices to overcome this.

Another challenge was integrating custom fonts from Google Fonts. Ensuring these fonts were correctly loaded and applied to the right elements required adjustments. By carefully following the documentation and using the @import method in the CSS, I verified the font-family settings in the Tailwind configuration to solve this issue.

Deploying the project on Netlify also presented initial hiccups, particularly with the build process and referencing all assets correctly. I reviewed the Netlify build settings, ensuring the correct build commands and publish directories were set. I also checked that all files and paths were correctly referenced in the HTML, which helped streamline the deployment process.

Overall, these challenges provided valuable learning experiences, and overcoming them has strengthened my problem-solving skills and knowledge of TailwindCSS and deployment processes.

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

In this QR code webpage project, there are a few specific areas where I would appreciate some guidance.

Firstly, I’m looking for feedback on improving the page’s accessibility. Suggestions on incorporating ARIA roles, labels, and enhancing color contrast would be particularly helpful to make the page more inclusive and user-friendly.

Secondly, I seek feedback on my use of TailwindCSS. I want to ensure I’m utilizing TailwindCSS efficiently and would appreciate any best practices or patterns I might have overlooked.

Lastly, tips on refining the deployment process to Netlify would be beneficial. Specifically, I’m interested in setting up continuous deployment and handling environment-specific configurations to streamline the deployment process.

Overall, any feedback in these areas would be greatly appreciated and would help enhance the quality and performance of my project.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Manjunatha C•150
    @manjunathagee
    Posted about 1 year ago

    Use relative units like rem instead of px

    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

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