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

Page responsive with HTML and CSS

Bruno L L Oliveira•180
@BrunoleonardoDev
A solution to the Huddle landing page with a single introductory section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


(PT-BR) Tentei colocar duas medidas de Media Queries, uma de 375px e outra de 820px. Mas não consegui manter as duas ativas ao mesmo tempo. Não sei se é possivel fazer isso acontecer.

(EN) I tried to put two measures of Media Queries, one of 375px and another of 820px. But I couldn't keep both active at the same time. I don't know if it's possible to make this happen.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    Fala Bruno, beleza?

    Dei uma olhada aqui no seu repositório e abri o código da pasta 07, eu não vi a media query de 375px, mas dá pra colocar duas média queries sim, basta que existam propriedades difode uma média pra outra pra que haja mudança. Eu já tive problemas com mais de cinco media queries que aí parava de funcionar não sei pq, mas com duas funciona sim.

    Eu vi que você fez várias pastas, não se se fez isso pra ter cada versão do código salva. Caso seja esse o motivo, eu tbm já fiz essa mesma coisa, mas dps descobri que dá pra baixar a versão do repositório com cada commit e baixar a pasta exatamente igual ela era no momento do commit. Isso é ótimo pq se vc estragar o código é só baixar a pasta inteira do commit que estava bom e trabalhar em cima disso e fazer um novo commit por cima do último. Pra baixar essa pasta basta ir no histórico de commit no Github.

    Espero ter ajudado, continue no foco 👏

    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

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