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

Blog preview card

Mohamed-Oday•190
@Mohamed-Oday
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Luam Belay•40
    @LuamB
    Posted about 1 year ago

    Hola 👋

    congrats on your design, which is very close to the design!

    Awesome aspects of your solution 🤩

    • Use of CSS custom properties (variables)
    • Use of transition

    Stuff to improve 🤓

    • You can define font-family once in the <body> element to avoid repetition and only define font-weight for each <h1> and <p> element:
    body {
        font-family: "Figtree", sans-serif;
        ...
    }
    
    h1.title {
        font-weight: 800;
        ...
    }
    
    p.description {
        font-weight: 500;
        ...
    }
    
    • In order to improve accessibility, you can use semantic HTML5 and you can use the BEM naming convention for your CSS classes to improve reusablility and code-sharing, e.g.:
    <body>
        <main class="container">
            <article class="blog-card">
                <img 
                    class="blog-card__image"
                    src="assets/images/illustration-article.svg" alt="#" 
                >
                <ul class="blog-card__category">
                    <li>Learning</li>
                </ul>
                ...
                <figure class="author">
                    <img 
                        class="author__image"
                        src="assets/images/image-avatar.webp" alt="#" 
                    >
                    <figcaption class="author__name">Greg Hooper</p>
                </figure>
            </article>
        </main>
    </body>
    
    • You can remove the <div class="attribution"> element (included in the starter package of each challenge) from your final solution, because it's not included in the design.

    I’m a beginner, but I hope my feedback is still valuable for you. I would appreciate if you could mark my comment as helpful if it was! 🙏

    Let me know if you have feedback on my comment or any questions and I'll do my best to respond.

    
Happy coding! 💻

    Marked as helpful
  • Abdullah Zafar•180
    @ei-abdullah
    Posted about 1 year ago

    Your work is outstanding, but I see you didn't work on proper README.md file as I think it serves a great purpose in explaining your project.

    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

Oops! 😬

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

Log in with GitHub