Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
10
Comments
9
Nathan Orobor
@omarnate1

All comments

  • P
    MikDra1•7,450
    @MikDra1
    Submitted 11 months ago

    Responsive social proof section - MikDra1

    1
    Nathan Orobor•150
    @omarnate1
    Posted 11 months ago

    hello, please check the live site, its down.

  • Thiago Lorhan•150
    @Thiagouh
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    I better understood the use of Grid and I intend to continue using it to understand more.

    What challenges did you encounter, and how did you overcome them?

    my problem was dealing with the inversion of positions of some cards present, but I managed to solve it by persisting.

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

    Any feedback on the project is welcome!

    Responsive Testimonials Grid Section with Tailwind CSS

    #tailwind-css
    1
    Nathan Orobor•150
    @omarnate1
    Posted 11 months ago

    very nice work, comparing it with the original design, you can make some adjustments to position it at the center.

  • Natthaphong Thongphueng•200
    @DearNatthaphong
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    Having issues with drop-shadow in Tailwind CSS. Welcome to any suggestions.

    What challenges did you encounter, and how did you overcome them?

    Having issues with drop-shadow in Tailwind CSS. Welcome to any suggestions.

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

    Having issues with drop-shadow in Tailwind CSS. Welcome to any suggestions.

    Having issues with drop-shadow in Tailwind CSS.

    #tailwind-css
    1
    Nathan Orobor•150
    @omarnate1
    Posted 11 months ago

    clean work mate, keep it up

    next time try and spare a few minutes to edit the readme-template and readme files to have your details.

    overall, job well done.

  • SmartAce•390
    @Smart-Ace-Designs
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    Learning new CSS tricks such as adding spacing between letters and adjusting line height. What I would do differently is handle the dual image differently. I believe the solution is to use the element, but I could not figure out how to map its functionality to the Astro equivalent - so I used the "hidden" declaration instead which is not ideal.

    What challenges did you encounter, and how did you overcome them?

    Spend way too much time tweaking spacing, text size, text weight, etc. Perhaps Figma might help.

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

    Using the Astro component to select different images based on the screen size. The documentation, that I found, does not seem to explain how to do this (assuming it is even possible to do with this component).

    Product preview card build with Astro and Tailwind CSS

    #astro#tailwind-css
    1
    Nathan Orobor•150
    @omarnate1
    Posted 11 months ago

    Nice job, well done. Very nice and clean codes.

  • James Brown•260
    @jamesbrown173
    Submitted 12 months ago

    Simple-recipe-page

    #tailwind-css
    1
    Nathan Orobor•150
    @omarnate1
    Posted 12 months ago

    Nice work, but take a little time to edit your README.md to have your details. I looked at your codes and the README.md files and template are all the same.

    Marked as helpful
  • Nathan Orobor•150
    @omarnate1
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    nothing new

    What challenges did you encounter, and how did you overcome them?

    none

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

    none

    Responsive design using css flex-Box and media query

    2
    Nathan Orobor•150
    @omarnate1
    Posted 12 months ago

    The solution includes semantic HTML with correct usage of elements like <header>, <main>, <footer>, and <nav>.

    To improve, verify that semantic elements are used where applicable, such as <article> for independent content sections.

    For accessibility, check for ARIA roles, alt attributes on images, and proper labeling of form elements.

    Use landmarks to improve navigation for screen readers and ensure sufficient color contrast. The layout uses responsive units and media queries effectively.

  • yosuef mohamed•80
    @yousef89
    Submitted 12 months ago

    social links profile

    #next#react#tailwind-css
    1
    Nathan Orobor•150
    @omarnate1
    Posted 12 months ago

    nice job, well done

  • yosuef mohamed•80
    @yousef89
    Submitted 12 months ago

    blog card project

    #next#react#tailwind-css
    1
    Nathan Orobor•150
    @omarnate1
    Posted 12 months ago

    nice and neat job.

  • dsaneshaikh•40
    @dsaneshaikh
    Submitted 12 months ago

    Used Flex and Basic CSS

    1
    Nathan Orobor•150
    @omarnate1
    Posted 12 months ago
    1. Semantic HTML: The solution effectively uses semantic HTML, enhancing both structure and accessibility.
    2. Accessibility: The design is accessible, with clear improvements made for screen readers.
    3. Responsive Layout: The layout is responsive, and looks great on various screen sizes.
    4. Code Quality: The code is well-structured, readable, and highly reusable.
    5. Design Adherence: The solution closely follows the original design, ensuring visual consistency.
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