Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
32
Comments
617
Abdul
@Samadeen

All comments

  • Uzochukwu Cecilia Oloh•50
    @Nsebo
    Submitted over 1 year ago

    Blog preview card built using simple HTML and CSS

    4
    Abdul•8,560
    @Samadeen
    Posted over 1 year ago

    Hello Nsebo

    Great work on completing this challenge. Cheers!! 🎊🎊

    Some adjustments are needed to place your container in the middle properly.

        display: grid;
         place-content: center;
         min-height: 100vh; 
    
    

    I hope to see more solutions from you.

  • 👾 Ekaterine Mitagvaria 👾•7,860
    @catherineisonline
    Submitted about 3 years ago

    REST Countries API with color theme switcher

    #react
    14
    Abdul•8,560
    @Samadeen
    Posted over 2 years ago

    Hello Catherine... You did beautifully well on this project, can you kindly recommend resources to learn React

  • Woodrow Martyr•120
    @wmartyr
    Submitted almost 3 years ago

    Used HTML, CSS, and Flexbox.

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey Woodrow!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="card"> instead of <div class="card">.
    • Your footer should be <footer class="attribution"> instead of <div =attribution>
    • Images must have alternate text - Its hard for screen readers to pick up messages from images without alt text.. Its always advisable to include alt text to aid screen reader

    This should fix most of your accessibility issues.

    • For your design here is a tip to center your container both vertically and horizontally display: grid; place-content: center; min-height: 100vh;

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • Adejokun Ibukunoluwa•20
    @IAdejokun
    Submitted almost 3 years ago

    Responsive QR Code Component

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey Omo Iya mi!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="content"> instead of <div class="content">.
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <h5 id="top">Improve your front-end skills by building projects</h5> should be <h1 id="top">Improve your front-end skills by building projects</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • James Kofi Myers•660
    @kinjames
    Submitted almost 3 years ago

    nft-preview-card-component

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="card"> instead of <section class="card">.
    • Your footer should be <footer class="attribution"> instead of <div =attribution>
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <h1 class="big-text"> Equilibrium #3429 </p> should be <p class="big-text"> Equilibrium #3429 </h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • MohammedC4r•10
    @MohammedC4r
    Submitted almost 3 years ago

    NFT Card - Using SASS, BEM

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="card"> instead of <div class="card">.
    • Your footer should be <footer class="attribution"> instead of <div =attribution>
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <h2 class="card__heading">Equilibrium #3429</h2> should be <h21class="card__heading">Equilibrium #3429</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.
    • Images must have alternate text - Its hard for screen readers to pick up messages from images without alt text.. Its always advisable to include alt text to aid screen reader

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • Max•120
    @Kypac-Max
    Submitted almost 3 years ago

    Responsive Order Summary by Max

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    • I noticed your container is not aligned vertically and horizontally.. i.e is not at the center of your webpage.. That can be corrected by setting display:flex; align-items:center; justify-content:center;

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

  • Yunus Yusuf•20
    @Yunishello
    Submitted almost 3 years ago

    Html for the makeup, css for custom styling, Bootstrap, and JavaScript

    #bootstrap
    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="row"> instead of <div class="row">.
    • Your footer should be <footer class="attribution"> instead of <div class="attribution">.
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <p class="qoute"> "Please click the button below to get an advice." </p> should be <h1 class="qoute"> "Please click the button below to get an advice." </h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

  • Chaitali•10
    @chaitalikarmakar
    Submitted almost 3 years ago

    HTML5, CSS, Flexbox

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="background-layout"> instead of <div class="background-layout">.
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <h3>Improve your front-end skills by building projects</h3> should be <h1>Improve your front-end skills by building projects</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

  • Surajit Shaw•10
    @SURAJITSHAW
    Submitted almost 3 years ago

    qr code component

    #itcss
    2
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="card"> instead of <div class="card">.
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <h3>Improve your front-end skills by building projects</h3> should be <h1>Improve your front-end skills by building projects</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • Edward Rangel•20
    @ledxs
    Submitted almost 3 years ago

    flexbox pseudoelements

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="container"> instead of <div class="container">.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • Gustavo Rivera•10
    @SebRivmor
    Submitted almost 3 years ago

    Card_QR

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    ** ¡Hey! ** Saludos 🥂 Al completar este desafío ...

    Primero trabajemos en sus problemas de accesibilidad.

    • El documento debe tener en el punto de referencia principal" Básicamente significa que su HTML debe estructurarse de manera más semántica y el formato correcto debe ser su <Header> ... ... ... </main> y, por último, su <footer> .... </footer> , por lo tanto, debe usar <main class = "contenedor"> en lugar de <div class = "contenedor"> . -La página debe contener un encabezado de nivel uno 'básicamente significa que su html debería tener una navegación de ayuda h1 de ayuda, por lo tanto<h2> mejorar sus habilidades front-end construyendo proyectos </h2>debería ser<h1 > Mejore sus habilidades de front-end creando proyectos </h1>y también debe bajar ordenado cuando esté utilizando los encabezados h1 hasta h2 hasta h3, y así sucesivamente.

    Esto debería solucionar la mayoría de sus problemas de accesibilidad.

    . Independientemente de que lo hicieras increíble ... ** Espero que encuentres esto útil ** ... ¡feliz codificación!

  • Payal Sasmal•20
    @PayalSasmal10
    Submitted almost 3 years ago

    Nothing

    3
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="img-qr"> instead of <div class="img-qr">.
    • Your footer should be <footer class="attribution"> instead of <div =attribution>
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <p class="bold-para">Improve your front-end skills by building projects</p> should be <h1 class="bold-para">Improve your front-end skills by building projects</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.
    • Images must have alternate text - Its hard for screen readers to pick up messages from images without alt text.. Its always advisable to include alt text to aid screen reader

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • Pedro•120
    @pedrommb7
    Submitted almost 3 years ago

    Single price grid component

    #sass/scss
    2
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="grid"> instead of <div class="grid">.
    • You should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

  • Khadija Hashmi•200
    @khadijahashmi2
    Submitted almost 3 years ago

    attempting to use css grid :D

    2
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="container"> instead of <div class="container">.
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <p>Join our Community </p> should be <h1>Join our community</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    • You can use flex or grid to center your container horizontally and vertically.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

  • Momoh Abdulrahim Remi•40
    @Brodaremi
    Submitted almost 3 years ago

    Responsive landing page using css

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main id="container"> instead of <div id="container">.
    • Your footer will be <footer class="attribution"> instead of div class="attribution">.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • Anthony Guilherme•190
    @oAnthonyG
    Submitted almost 3 years ago

    landing page used html and css only

    2
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="container-card"> instead of <div class="container-card">.
    • And your footer should be <footer class="attribution"> instead of <div class="attribution">.

    This should fix most of your accessibility issues.

    -You can use flex or grid to center your container horizontally and vertically.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    Marked as helpful
  • Ivan Aguilar•30
    @Ivan96318
    Submitted almost 3 years ago

    Responsive landing page using css

    1
    Abdul•8,560
    @Samadeen
    Posted almost 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="row"> instead of <div class="row">.
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <h2> Order Summary</h2> should be <h1 >Order Summary</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

    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