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

Blog preview card using CSS flexbox and media query

Daniele Morello•100
@DanieleMorello
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 am satisfied that I made the responsive card.

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

The challenge was centering the card in mobile and desktop mode, which was overcome through the 'use of flexbox and mediaquery.

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

I would like to know a better solution than my.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ayua Michael•530
    @TorCanHack
    Posted about 1 year ago

    Congratulations on finishing the challenge.

    Good job on making the webpage responsive.

    I noticed a few things you might find beneficial to incorporate into your coding.

    I noticed you included <h1> <h2> and <h3> tags. However, you did not use them in chronological order. Using the header tags properly is important as they provide structure to the webpage and are also utilized for accessibility features by screen readers. Thus, <h2> comes after <h1> and <h3> comes after <h2> and so forth.

    <h1> is reserved for the most important heading in the document and <h6> is for the least important. When you use the headers tags properly the webpage is better structured and easily accessible.

    I hope you find this helpful in structuring your webpage.

    happy coding!!!

  • Skalex Stuch•210
    @mussino
    Posted about 1 year ago

    Your provided HTML code includes some semantic HTML elements, such as <h1>, <div>, <img>, <p>, <strong>, and <a>. These elements convey the meaning and structure of the content to assistive technologies and search engines.

    Here's a breakdown of some of the key semantic elements in your code:

    <h1>: Represents the main heading of the page. <div>: Used for grouping content and applying styles. <img>: Represents an image within the document. <p>: Represents a paragraph of text. <strong>: Represents strong importance, typically rendered as bold. <a>: Represents a hyperlink.

    Overall, your code seems to use semantic HTML elements effectively. However, you can further enhance semantic structure by ensuring that elements are used appropriately to convey the meaning and structure of your content. Additionally, you may consider using semantic elements like <header>, <nav>, <main>, <article>, <section>, and <footer> to provide additional meaning and structure to your document.

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