Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
2
Comments
2

Luam Belay

@LuamBBerlin40 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

  • Responsive Blog preview card using Flexbox, viewport units and clamp()


    Luam Belay•40
    Submitted about 1 year ago

    1 comment
  • Semantic HTML5, CSS nested Flexbox


    Luam Belay•40
    Submitted about 1 year ago

    1 comment

Latest comments

  • Mohamed-Oday•190
    @Mohamed-Oday
    Submitted about 1 year ago

    Blog preview card

    2
    Luam Belay•40
    @LuamB
    Posted 12 months 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
  • Ankit04042001•50
    @Ankit04042001
    Submitted about 1 year ago

    QR-CODE-COMPONENT-MAIN

    1
    Luam Belay•40
    @LuamB
    Posted about 1 year ago
    • you might want to remove div.attribution
    • you might want to improve spacing between img, h1 and p to match the design
    • you might want to reduce border-radius of the img (border-radius of qr is ok, I think)
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

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

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

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

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

Oops! 😬

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

Log in with GitHub