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

Meu primeiro teste do FrontendMentor, um card responsivo em HTML e CSS

Diovanni-ls•50
@Diovanni-ls
A solution to the Blog preview card 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?

fiquei orgulhoso de ter conseguido construir toda a estrutura se problemas, sendo o meu primeiro projeto aqui. Gostei muito do processo de criação e consegui aprender coisas novas.

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

tive dificuldades em fazer a responsividade para telas menores, o que me forçou a procurar novas saídas e aprende novos métodos.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    MikDra1•7,450
    @MikDra1
    Posted 9 months ago

    Here is how you can make your card responsive easily

       .card {
           width: 95%;
           max-width: 42.5rem;
       }
    

    On smaller screens, the card will occupy 90% of its parent (such as the body), but once it reaches 42.5rem (680px), it will remain like that.

    I hope this tip was useful to you! 💗💗💗

    Great work, and keep it up! 😁😊😉

    Marked as helpful
  • Adriano•42,890
    @AdrianoEscarabote
    Posted 9 months ago

    Hi Diovanni-ls, hope you're doing well! I loved how your project turned out, but I’ve got a few suggestions that could be useful:

    Using Flexbox or Grid on the body to center elements ensures a more responsive and adaptive layout, fitting different screen sizes seamlessly. It avoids manual calculations and constant adjustments needed with margin, padding, or absolute positioning. These techniques provide more consistent alignment and simplify the code.

    flexbox:

    body {
        display: flex;
        justify-content: center;
        align-items:  center;
        min-height: 100vh;
    }
    

    grid:

    body {
        display: grid;
        place-content: center;
        min-height: 100vh;
    }
    

    The rest is fantastic.

    Hopefully, you'll find it helpful. 👍

    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