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

HTML5, CSS3, flexbox, mobile-first workflow

Kiko•20
@Lushifer666
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had a hard time starting, since this is my first project. What I did is I started on resizing the image first before styling the other elements of the page. How will you guys start and what are the best advice you can give on starting projects?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hello, Kiko! 👋

    Congratulations on finishing your first Frontend Mentor challenge! 🎉

    In addition to @EdwinSch has said earlier, I would recommend using the modern CSS reset by Piccalilli. It focuses on accessibility and is more modern than the one you currently used.

    One suggestion I have is to improve the alternative text. Alternative text should not be hyphenated (like code). Also, I suggest giving more information about the QR code. This way, the users will know exactly what the QR code is doing after they scan it.

    That's it! I hope you find this useful! 😊

    Marked as helpful
  • P
    Ed•720
    @EdwinSch
    Posted almost 3 years ago

    Hi! Congratulations on your first solution. :) About your question; there isn't really a right or wrong answer here as every project had it's own requirements. Building out a massive multipage application would have a very different approach compared to this single component. But in my overal experience: structure is the keyword. Start a project by thinking of, or sketching out, what your approach is going to be. Break down the design in a Component, Flex or Grid structure (whatever your preference) so you get a better view of how to build your layout. Logically structure any files that you will need or have recieved and last but not least; decide if you are going with mobile- or desktop first responsiveness.

    Happy coding!

    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

Oops! 😬

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

Log in with GitHub