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

BlogCard using Grid and Flex

aztromel•40
@aztromel
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?

I really liked that I was able to grasp the concept of grid and flex better in order to align the card right in the center without any issues, I was also able to align the content inside the card correctly without any issues. However, I really had issues trying to edit the svg and making sure the card was responsive in mobile devices. I also feel I could've done better in building the animation.

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

My biggest challenge by far was trying to make the design responsive, but I tried solving this by using a predetermined width and also making the font sizes responsive enough.

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

I would like help in understanding a better and more efficient way of building a responsive design for this solution. Is there a way to change the width without using media queries?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,830
    @danielmrz-dev
    Posted about 1 year ago

    Hey there! 🙋🏽‍♂️

    Congrats on completing the challenge! ✅

    Your project looks fantastic!

    Here's a tip to make it even better:

    Using margin and/or padding isn't always the best way to center an element. Try this method to center an element vertically and horizontally:

    📌 Apply this CSS to the body (skip position or margins to make it work correctly):

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

    Hope this helps!

    Keep up the great work!

  • JOSIANE FERMAO•170
    @josifermaodev
    Posted about 1 year ago

    You can make your design responsive without using media queries by using a few different approaches. Here are a few techniques that can help:

    1. Flexbox and Grid Layout:

    Both are great tools for creating flexible layouts that automatically adjust to the screen size.

    2. Relative Units:

    Using relative units like em, rem, vw, and vh can make your design more adaptable to different screen sizes.

    em and rem: Proportional to the font size of the element or root.

    vw and vh: Proportional to the width and height of the viewport.

    3. CSS Functions:

    CSS functions like calc(), min(), max(), and clamp() help you create dynamic values ​​that adjust to the context.

    4. Aspect Ratio:

    Maintaining the aspect ratio of elements can help you create designs that automatically adjust.

    5. CSS Custom Properties (Variables)

    Using CSS variables allows you to dynamically adjust your design based on global variables.

    These techniques can help make your design more flexible and adaptable to different screen sizes without relying solely on media queries.

  • gajbos99•170
    @gajbos99
    Posted about 1 year ago

    Good job! Try some padding between some of the text elements and it looks exactly the same.

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

Oops! 😬

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

Log in with GitHub