Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 17 days ago

Blog Preview Card using HTML and CSS

Lexi Crotts•20
@Lanncrotts
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?

Ability to do it quickly compared to when I first started. Also not having to look up how to do things anymore. They're starting to become second-nature as I keep practicing.

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

I realized that I needed to add more into the media query section compared to Project 1 in order for things to look right. Once I figured that out and what to change, I was good to go!

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

I feel pretty confident in most of my code. The main thing I'm trying to work on now is being more organized in my code, so I'll definitely take any organization tips for CSS. While mine may not line up perfectly with the solution web page, I'm happy with it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•4,230
    @thisisharsh7
    Posted 17 days ago

    Great job on your Blog Preview Solution! Your HTML and CSS are well-structured, and it's good to see your confidence growing with practice.

    Some suggestion:

    1. CSS Organization: Group related styles under clear comment sections (e.g., /* Typography */, /* Layout */, /* Media Queries */). This makes your CSS easier to navigate. Consider using a CSS preprocessor like SASS for nesting and modularity in future projects.

    2. Font Size Adjustment: For mobile view, reduce font sizes slightly to enhance readability. In your media query (@media (max-width: 600px)), try setting .preview .title to 1.25rem, .main-content to 0.75rem, and .credit-box .author to 0.5rem.

    3. Consistency: Standardize margins and padding (e.g., use 8px consistently instead of mixing 8px and 10px). This improves visual harmony.

    Keep practicing, and your code organization will become even more intuitive! Excellent work overall!

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