Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 3 months ago

Blog preview

Vaishnavi-194•80
@Vaishnavi-194
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?

This is my second handson challenge. For the 1st challenge I needed some reference to complete, for this challenge I tried it without any reference.

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

fonts were provided as .ttf files. But I have imported the google fonts. Learning on how to use ttf files.

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

All suggestions are welcomed. Thank you in advance.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Andrea Selmi•160
    @andreaselmi
    Posted 3 months ago

    Hi there! Great work so far, you're doing well! 😊

    Just a few quick suggestions (if I may) to help you improve:

    Use rem instead of px: This helps make your website more accessible, especially when users adjust their browser’s font size. It's a good habit to start using rem units early on!

    Make class names more descriptive: Class names like text1 or text2 make the code harder to read and understand. Try using more meaningful names like card__title or card__description. It helps keep your CSS organized and easier to maintain. You can check out this naming convention: https://getbem.com

    Watch out for spacing and border values: For example, in this code:

    #article {
        width: 100%;
        border-radius: 13px;
        margin-bottom: 15px; 
    }
    

    You've used different values that don’t follow design values. A good rule of thumb, by the way, is to use multiples of 4 (like 12px, 16px, 20px…) for consistent spacing and a cleaner design.

    Avoid using IDs in CSS: It's generally better to use classes instead of IDs when styling elements. Classes are more flexible and follow best practices, especially when your project grows.

    Keep going 💪 Let me know if you ever want more help or feedback :)

    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

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