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

Blog Preview Card using flexbox

joacomenda•170
@joacomenda
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'm most proud of how it ended up looking in desktop, I would try and intregrate more media queries so I can make it more responsive to mobile devices

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

I found difficult to center the container of all the card content to the center of the page, I contained everything into a section element, then I gave it height. Then I styled it using CSS, adding a flexbox to align it horizontally and vertically.

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

I'm still finding another to put the container in the center of the page, if you have another way, plase share it.

Also, what is the best practice to make a responsive design, to make it look good on mobile

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Si1entERA•450
    @Si1entERA
    Posted over 1 year ago

    Hello @joacomenda.

    Congratulations on the completion of your project.

    I'm still new and I'm not at the level of the other developer here but I'll pass on some advice I recently received from @danielmrz-dev.

    "Try using<h1> to <h6> tags for headings instead of<p> since they are used for paragraphs. When it comes to headings. This can improve the structure of your HTML and make it look cleaner."

    This is one of my mistakes I've made a lot and I hope you find this helpful. Happy coding.

    Marked as helpful
  • Saeed Bin Mizan•80
    @BluffSet7340
    Posted over 1 year ago

    Your method of using the section and styling it accordingly works just as well. But if you want another way, you could try and place the image, the body, and the avatar and author name into 3 separate div elemtents and then add the CSS properties on the body element. That will target all the div elements inside of the body and center the content horizontally and vertically.

    For responsive design, it depends. Some people like to start with a mobile first workflow, where they design the webpage for mobile devices first and then use media queries to adjust for desktop sizes. What I did was design it for desktop first and then reduced the width accordingly when the screen width was reduced to that of mobile devices

  • fhelix09•40
    @fhelix09
    Posted over 1 year ago

    Thanks for this I learn new by viewing your script.

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