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

A Blog review card using HTML and CSS

robinsonexe•80
@robinsonexe
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 learnt better about how to use classes to apply styles to different elements of the same type but in the same container i.e( multiple paragraph elements having different styles). probably next time rather than using divs I would experiment using a non-semantic in-line element (span) just to see the difference and which is more suitable.

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

A challenge I faced but necessarily did not overcome is properly centering the main content, I ended up using a margin but I believe there would be better and more suitable methods to do this.

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

A more suitable way to centering elements, not just centering but positioning elements in the correct places I would need to for various projects, like I mentioned earlier most times I use margins, paddings, text-align and align items but I believe these are mostly makeshift solutions

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • rawrisotto•240
    @rawrisotto
    Posted about 1 year ago

    Hi there!

    There is a browser extension called PerfectPixel which you can use to compare against the design image. It was recommended to me by a fellow Frontend Mentor user and has helped me so far. I hope this suggestion will be useful to you for your upcoming challenges or projects :)

    Marked as helpful
  • mijeong•160
    @snakechickensoup
    Posted about 1 year ago

    You can solve it by using flex or position when you want to center-align a component

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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