Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

First try making a Responsive Website using display flex

Diego Guaglianone•30
@DiegoGuaglianone
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?

What are you most proud of?

I'm most proud of completing my first responsive website. Despite facing challenges with media queries, I managed to overcome them and create a functional layout. It's a significant achievement for me as a beginner in web development.

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

What would you do differently next time?

Next time, I would allocate more time to understanding and implementing media queries effectively. I realized that they play a crucial role in creating responsive designs, and mastering them early on would save time and effort in the long run. Additionally, I would seek out more resources and guidance to improve my skills further.

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

Areas where I need support

As this is my first responsive website, I'm still learning and exploring different techniques. I would appreciate support and guidance from experienced developers on how to enhance my understanding of media queries and build more sophisticated layouts. Any advice or feedback on improving my coding practices and design skills would be highly valuable to me.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bernardo Poggioni•7,030
    @R3ygoski
    Posted over 1 year ago

    Olá Diego, parabéns pela conclusão do seu projeto ele ficou muito bom.

    Começarei pela sua duvida quanto a media query. Geralmente eu gosto de trabalhar no mobile-first workflow, pois é mais intuitivo pois só precisa ser usado o min-width. Nele nós começamos fazendo a página nos baseando em designs mobile, geralmente 320px e 375px, e vamos aplicando as media queries para telas maiores, geralmente isso faz com que eu precise usar apenas uma media query, então recomendo muito que você dê uma olhada em como fazer projetos mobile-first.

    Outra dica, que é em questão de organização, evite ao máximo usar style inline e style internal, pois isso deixa o arquivo do HTML muito verboso. Como seu projeto é simples e pequeno, isso não vai afetar muito, mas em projetos maiores você veria o quão problemático isso pode ser tornar, e sem contar que é uma boa prática você usar o CSS external, isso é, deixar um arquivo separado para o CSS.

    Agora sobre algumas outras coisas. Quando você for utilizar tanto o font quanto o font-size, evite de passar valores em px, isso porque, px é um valor absoluto, o melhor é passar a medida rem, que é uma medida relativa. Ela é boa para ajudar na acessibilidade, pois ela se adapta as configurações de fonte do usuário.

    Uma outra dica seria a de utilizar max-width e min-width para delimitar o tamanho máximo e o tamanho mínimo do seu card.

    E novamente, parabéns pelo seu projeto, ele ficou muito bem feito, continue praticando e se aprimorando cada vez mais, caso algo que eu tenha dito não tenha ficado claro, por favor, comente aqui embaixo.

  • Adnan•110
    @admztech
    Posted over 1 year ago

    -Semantic HTML5 markup -CSS3 custom properties -Mobile-first workflow

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

Oops! 😬

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

Log in with GitHub