Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

QR Code Component with Flexbox and LESS

less, accessibility
Joe•10
@Joe-Whitehead
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, This is my first attempt at HTML/CSS (Using LESS pre-processor) since not touching anything web related for about 5/6 years. Getting started in this I found I had forgotten almost everything, and it was interesting discovering the flexbox features.

My question to the community is how do you decide what frameworks you are going to use for a particular project? and do you pre-plan or dive straight in and figure it out as you go?

Thanks, Joe

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nneoma Njoku•1,210
    @SatellitePeace
    Posted almost 3 years ago

    Hello @Joe-Whitehead and congrats on your return to web dev

    As for your questions I am assuming the frameworks you are talking about are css frameworks like scss, less, bootstrap, tailwind etc

    The framework you use all depends on how large the project is, how many pages, the project will have and how many sections the project will have

    Personally when dealing with large project I usually recommend a css preprocessor like scss or less

    Then if you are building a medium project or a prototype for a big project you can use a framework like bootstrap to speed things up

    But in all it is always best to use vanilla css and preprocessors like scss and less

    As for your second question, it is always best to visualise the project in your head try to build it in your head by so doing you will be able to figure out the key structures and how to organize your elements and which element to give a classname

    As you code there is always going to be a point where you will have to figure things out as you go, but thinking about the strategies to use before diving in makes your work easier and reduces the chances of you having to figure things out as you code

    I hope this helps

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