Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
20
Comments
10
Adebukola Adeyinka Omowole
@Adebukol

All comments

  • Mageshwari Balaguru•170
    @Mageshwari-Balaguru
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    This layout took me around 6 hours. Next time will try to reduce the time. also try to use some CSS methodologies like BEM. I just recently come to know there were some methodologies is there which will make our code more readable, understandable.

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

    In the flex container, .items-container the paragraph text which is in speech class was not occupy the whole size. i tried max-width to fit-content - won't work, so deleted that.

    Testimonials-grid-section

    1
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted 12 months ago

    your code uses semantic HTML effectively with elements like <main> and <footer>. The use of <h1> tags for the primary headings in each testimonial is appropriate, emphasizing the importance of the content. Improvements: Consider replacing some of the <div> elements with more semantic tags. For example, <section> could be used for each .items-container to better indicate that each section is a standalone block of content. 2. Accessibility Strengths: The alt attributes are correctly used for images, which is crucial for screen readers and improves accessibility. Improvements: The headings structure could be improved by ensuring there’s a logical flow from <h1> to <h2> (or further down if needed) for better accessibility. For instance, having multiple <h1> tags might not be ideal; consider using <h2> for subsequent headings. 3. Responsive Layout your code appears to be structured in a way that could be easily adapted for responsiveness, especially with the container and wrapper classes.

  • Konrad•370
    @konradbaczyk
    Submitted 12 months ago

    Four card feature section using grid.

    2
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted 12 months ago

    Welldone for making efforts to get this done. semantic HTML followed Layout not bad Readable code Slight differences between the design and the solution. layout responsive. great job keep up the good work it can only get better

  • Fabiana•100
    @fabianajmge
    Submitted about 1 year ago

    product-preview-card

    1
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted 12 months ago

    Welldone, however your live site does not meet up with the design. your code does not include semantic HTML, Your code is responsive on all devices, nice work there. great effort you've put into this.

  • Radwan-Sghir•100
    @Radwan-Sghir
    Submitted 12 months ago

    solution for recipe page problem

    1
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted 12 months ago

    Nice work It included semantic html. It is accessible The solution differs from the design, the layouts are way bigger and the responsiveness needs to be worked on as my mobile view of the site was not looking good at all. But in all great job.

  • Shoaib Bin Rashid•120
    @Shoaib-Bin-Rashid
    Submitted 12 months ago

    Social links profile

    1
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted 12 months ago

    well Shoaib,The social media profile webpage is visually appealing, with a clean design, intuitive navigation, this is quite impressive. keep up the good work

    Marked as helpful
  • Jose Sebastian•300
    @wolf2lyon
    Submitted 12 months ago

    Blog-preview

    #accessibility
    1
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted 12 months ago

    great work jose, keep soaring

  • Pablo Adriano•10
    @PabloAguiar27
    Submitted 12 months ago

    Página destinada usando FlexBox

    #accessibility
    1
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted 12 months ago

    Well done @pablo However here are a few things I can say regarding your design, it's uniquely yours but not in accordance with the design UI, I do not have access to your codes as well perhaps you used a repository name that didn't align with the design.

  • Aung Htoo Khine•40
    @aunghtookhine
    Submitted almost 2 years ago

    Responsive-newsletter-sign-up-form-with-success-message

    #bootstrap#typescript
    1
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted almost 2 years ago

    Nice trial, however your card height differs with the design. You didn't make use of enough padding, your border radius as well.

    Marked as helpful
  • saidi ali•270
    @alihydro
    Submitted almost 2 years ago

    testimonials-grid-section-main

    1
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted almost 2 years ago

    Nice trial, you can still fix the top margin

  • Stoica Claudiu•300
    @llr3v0ll
    Submitted about 2 years ago

    interactive-rating project

    3
    Adebukola Adeyinka Omowole•280
    @Adebukol
    Posted about 2 years ago

    well done, you can use the onclick function to style it js

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