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

blog preview card

sass/scss
Uxmal Cuellar•20
@UxmalCuellar
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?

Learning how to create a responsive design using the clamp function instead of media queries

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

Understanding the 'preferred value' in the clamp function took a while for me to grasp, but after reading the docs and playing around with it, I finally got it in the end

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

How well did I structure my HTML for accessibility

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mustafa Sen•3,180
    @mustafasen97
    Posted about 1 month ago

    Your design is quite nice and your HTML codes are semantically good. However, there are a few more improvements that can be made in this regard.

    First of all, it would be correct to put all the content except the footer section in the <main> tag.

    Example:

    <main>
    <article>
    
    Codes here
    
    </article
    </main>
    

    You can also use the <time> tag directly instead of the span in the date section and add the datetime property to this tag. The datetime property specifies the date and time of the text it contains.

    
    <time datetime="2023-12-21" id="publish-date">Published 21 Dec 2023</time>
    
    

    Apart from that, I think your codes are quite good. You can also look at the code structures of experts to improve yourself in semantic HTML.

    Marked as helpful
  • Mohamed ashrf•340
    @x-mohamed25
    Posted about 1 month ago

    Nice job! The structure is clean and matches the original design. One suggestion would be to improve the mobile responsiveness a bit. Keep it up!

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