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

Utilizei HTML e CSS

P
Carlos Eduardo Santos Oliveira•180
@Carlos-Eduardo-S
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 felt proud to have built the page with only basic instructions. Even though it's a basic project, completing it made me more confident in tackling future projects.

One thing I would do differently next time is to add more responsiveness. I didn't need to implement responsive commands on this page, but I hope to use them in other projects. I would also like to use more responsive units.

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

The biggest challenge I encountered was aligning the items. In the beginning, I couldn't style the image properly. I solved this problem by separating the image from the other stylable items and styling only the image first. I did one at a time until I finished the page.

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

I would like help primarily in areas related to responsiveness. I used the inspect bar to check how the page would behave on mobile, and it seemed normal. If you see any problems and could let me know, I would appreciate it. Also, if you could give me suggestions for responsive measures, I would be grateful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Piwko Marcin•200
    @PiwkoO
    Posted 4 months ago

    I would suggest to use English for naming and variables, so it would be more accessible to other people (you'll never know with who you'll end up working with) and include .gitignore file in repository.

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