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

Blog Preview Card

Naveen Kumar J•80
@Naveen-KumarJ
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feedback Welcome and Thanks in advance😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your Blog Preview Card project! It's a fantastic achievement to have brought your design to life. Here are some best practices to enhance your project further:

    • Responsive Design: Ensure your design is responsive across different devices. Consider using media queries to adapt the layout for different screen sizes. More on responsive design can be found here.

    • Semantic HTML: Use more semantic HTML elements to improve the structure and accessibility of your page. For instance, the blog content can be wrapped in an <article> tag. Learn about semantic HTML here.

    • CSS Efficiency: In your CSS, you can group selectors that share the same style properties to keep your code DRY (Don't Repeat Yourself). This practice enhances code readability and maintainability. More on CSS efficiency here.

    • Accessibility: Add descriptive alt text to your images to improve accessibility for screen reader users. More about web accessibility can be explored here.

    • Font Loading: Consider the impact of loading multiple font weights on performance. Loading only the required font weights can improve your page's load time. More on font optimization here.

    • Hover Effects: Great job with hover effects! Ensure that these effects also translate well on touch devices where hover isn't available. More on hover effects and touchscreens here.

    Keep up the great work, and continue pushing your boundaries in web development. Each project is a step forward in your journey, and you're doing wonderfully!

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