Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
5
Comments
193
mubizzy
@mubizzy

All comments

  • achrustowski•150
    @achrustowski
    Submitted almost 3 years ago

    Preview card component

    2
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    <a href=# class=ff-primary fs-100 fw-primary-regular remove the button element

    Hope it helps:).

    Marked as helpful
  • Rafi Mahmud Rizvi•130
    @RafiiMahmudRiizvii
    Submitted almost 3 years ago

    3-column preview card component

    3
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    good job @RafiiMahmudRiizvii just need need to some features for the card to be in the right position

    .container{
       align-items: center;
       justify-content: center;
    }
    

    Also, you need to work on your accessibility wrap your code in your <main> Tag

  • Dhabiri•60
    @Dhabiri
    Submitted almost 3 years ago

    Interactive rating component main

    2
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    nice job @Dhabiri I must say using a two-page for your card component is not the best practice.

    A page is enough you just need to understand the event listener for this part of the project.

    Also, you need to work on the semantic enclose your code in a <main> tag

    Marked as helpful
  • Zoruaq•30
    @Zoruaq
    Submitted almost 3 years ago

    3Column Solution

    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    nice job @Zoruaq but you still need to work on your accessibility issues.

    • you should add alt = " " to your <img> tags`
    <img src="images/icon-sedans.svg" alt = " ">
    
    <img src="images/icon-suvs.svg" alt = " ">
    
    <img src="images/icon-luxury.svg" alt = " ">
    
    

    hope it helps :)

    Marked as helpful
  • Blessing Oluwapelumi•20
    @blessingOluwapelumi
    Submitted almost 3 years ago

    RESPONSIVE LANDING PAGE WITH DROP DOWN MENU USING HTML,CSS,AND JAVASCR

    #angular#axios#bulma#sanity#chai
    2
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    nice work @blessingOluwapelumi you did a great job. about the hover features, you need to rotate the icon using CSS properties for Example.

    .dropdown:hover .dropdown__icon {
      transform: rotate(180deg);
    }
    
    .dropdown__icon {
      transition: .5s;
    }
    

    hope it helps :)

  • Princess Egbu•50
    @ronniiii-i
    Submitted almost 3 years ago

    Intro section with dropdown navigation

    2
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Also add alt=" " to your <img> tag

    Marked as helpful
  • JAHANZAIB IQBAL•80
    @jahanzaibiqbal
    Submitted almost 3 years ago

    Fontend-Mentor-3-column-preview-card-component

    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

  • P
    ania•330
    @ania221B
    Submitted almost 3 years ago

    4-card feature section with grid, flexbox and custom properties

    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

    Marked as helpful
  • Samuel Llibre Santos•400
    @Zyruks
    Submitted almost 3 years ago

    Stats Preview Component Card

    #accessibility#bem#gulp#sass/scss
    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge!

    Hope it helps:)...don't forget to mark it as helpful 👍

  • Lakshitha•110
    @lakshithaperera
    Submitted almost 3 years ago

    interactive-rating-component-main

    #stylus
    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

    Marked as helpful
  • Jordan•140
    @joanFaseDev
    Submitted almost 3 years ago

    Single Price Component using CSS Grid

    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

  • TechKami•310
    @NaskyiSan
    Submitted almost 3 years ago

    Responsive,BEM,CSS

    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

  • Yu-An•70
    @yuany2036
    Submitted almost 3 years ago

    Somewhat responsive social proof page

    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

  • Baldassare Pugliese•130
    @bpa03
    Submitted almost 3 years ago

    Ping Coming Soon Page (Sass HTML, Javascript)

    #sass/scss
    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

  • Alin Balog•200
    @Fabzus
    Submitted almost 3 years ago

    Ping single column coming soon page

    2
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

    Marked as helpful
  • Bernardo•10
    @BernardoCicchelli
    Submitted almost 3 years ago

    QRCode component

    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

  • Wiks•750
    @wiksmf
    Submitted almost 3 years ago

    Base appare coming soon page

    2
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

    Marked as helpful
  • Leroy Nnalue•220
    @sommmtoooo
    Submitted almost 3 years ago

    Tip Calculator App

    #sass/scss#semantic-ui#accessibility
    1
    mubizzy•1,520
    @mubizzy
    Posted almost 3 years ago

    Excellent job on this challenge! your report has a few issues though:

    1. wrap everything in your body in <main> or use semantics

    2.   it is a best practice to use both HTML 5 and ARIA landmarks to ensure all     content is contained within a navigational region.

    Hope it helps:)...don't forget to mark it as helpful 👍

    You can get more details here...click here

    Marked as helpful
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

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

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

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

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