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

Simple Blog preview card

Uttam Kalaria•40
@Uttam-Patel
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 was a beginner level challenge and I have solved it easily without any problems. But if anyone have any type of feedback then please share it on comment below.

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

This was a beginner level challenge and I have solved it easily without any problems.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted about 1 year ago

    Hello there!

    Congrats on completing the challenge! ✅

    Your solution is really impressive!

    I've got a couple of ideas (about how to use HTML better) that could make it even stronger:

    📌 First: Think about using <main> to wrap your main content instead of <div>.

    Imagine <div> and <span> in HTML as basic containers. They're good for holding stuff, but they don't tell us much about what's inside or its purpose on the webpage.

    📌 Second: Consider using <h1> for your main title instead of <h2>.

    It's more than just text size — it's about structuring your content effectively:

    • The <h1> to <h6> tags are used to define HTML headings.
    • <h1> is for the most important heading.
    • <h6> is for the least important heading.
    • Stick to just one <h1> per page – it should be the main title for the whole page.
    • And don't skip heading levels – start with <h1>, then use <h2>, and so on.

    These tweaks might not change how your page looks, but they'll make your HTML code clearer and help with SEO and accessibility.

    Hope that's helpful!

    Keep up the great work!

    Marked as helpful
  • nahuejandro•70
    @nahuejandro
    Posted about 1 year ago

    This code follows good accessibility and semantic practices, making it easier to understand for both developers and analysis tools.

    To ensure that your layout looks good on a range of screen sizes, you should implement responsive design techniques. Here are some suggestions to improve the responsiveness of your layout:

    1-Use Media Queries: Add media queries to adjust the layout for different screen sizes. This can help you optimize the design for both small and large screens.

    The HTML and CSS code provided is well-structured, with clear use of sections, classes, and ids. Is readable due to its clean formatting, consistent indentation, and use of descriptive class names.

    The use of CSS variables and class names like .category, .avatar, and .poster indicates a good approach towards reusability. This makes it easy to apply these styles to other elements in the project if needed. To enhance reusability further, consider creating more modular components that can be reused across different parts of the application.

    2-Instead of fixed widths, use percentages or relative units (e.g., vw, vh, em, rem) to make your elements flexible.

    3-You are already using flexbox, which is great for creating responsive layouts. Make sure all flexbox properties are used optimally.

    4-Ensure your images scale appropriately.

    Testing the layout on various devices and using browser developer tools to simulate different screen sizes will help you identify and fix any issues with responsiveness.

    The solution of the project is similar to the original project, only with some changes in the widths and heights, and it would be correct.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub