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

Mobile-first solution using CSS Flex, adaptive web

Alisa•30
@alisaTonga
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?

That's my first adaptive web. I stragle most with Css code aligning elements and trying to make it adaptive.

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

As i told that was my first time doing it, i found youtube video and did almost the same thing.

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

I think right now styling the web is my issue. I;m writting code but sometimes i dont complitely undersand consequences of some parts of code.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    yuval nisim•440
    @nisimi96
    Posted 10 months ago

    good job!

    i do think you wanna work on the flex\grid thing. as you can see you main object is off the center try to add and remove some staff because it small project not need to use main so you dont get confused. try to use display flex on body tag and keep it same just in css do body + justify content center and align items center maybe get you better position

    then use the .block as the organizer for the elements that come in side maybe even ! display flex > flex direction ; column that way you don't need to use <br> because all element will come one after one as there DNA is flex column

    love it i will give this challenge a try now to see what is my result

    keep it up , Yuval

    Marked as helpful
  • P
    🔅 Yuliya 🐈•330
    @O-Julia-O
    Posted 10 months ago

    Hello, Alisa!

    You are doing a great job!

    Here are some links which tells you more about aligning items on page.

    FlexBox: https://css-tricks.com/snippets/css/a-guide-to-flexbox

    Grid: https://css-tricks.com/snippets/css/complete-guide-grid

    Keep 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, SASS, 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