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

Static QR code component page using CSS Flexbox

tailwind-css, node
Celian4862•10
@Celian4862
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?

I'm most proud of using Tailwind CSS to successfully and easily style the static page.

I'd try to use a framework that would be unnecessarily complex for this project just to see how I can replicate static pages in it, such as in Next.js (particularly the React.js part of it) or Vike, or using APIs to retrieve the content such as with Elysia.js.

What challenges did you encounter, and how did you overcome them?
  • At one point, I couldn't figure out how to allow myself to change the boldness of text at any given point in the code. Turns out that I didn't have to make more custom classes and just combine the font-normal and font-bold Tailwind classes with the font-[Outfit] class.
  • Deciding how to place the margins around the texts and images was a bit of a dilemma since I was considering either splitting the margins between the elements or just placing the margin only on one side for each element.
What specific areas of your project would you like help with?

I'd like to know if semantic tags would make the website more accessible, and if so, I'd like to know where they should go on the code.

Edit 2025-02-07 9:42 UTC+0: I'd also like to learn how to improve my styling; for example, I was initially not sure how to apply the margins and ended up with the mb-* classes in the image and text elements.

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 Celian4862'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.