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

Olorunbunmi Olajumoke

@codesigner-jmk110 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

  • Price Grid Section

    #tailwind-css

    Olorunbunmi Olajumoke•110
    Submitted 8 days ago

    1 comment
  • Huddle Landing Page

    #tailwind-css

    Olorunbunmi Olajumoke•110
    Submitted 9 days ago

    0 comments
  • Review Page using Grids and Flexbox

    #tailwind-css

    Olorunbunmi Olajumoke•110
    Submitted 13 days ago

    0 comments
  • Responsive Grid Testimonial Section using Tailwind

    #tailwind-css

    Olorunbunmi Olajumoke•110
    Submitted 16 days ago

    1 comment
  • Responsive four card section using tailwind

    #tailwind-css

    Olorunbunmi Olajumoke•110
    Submitted 19 days ago

    1 comment
  • Responsive Product Card using Tailwind

    #tailwind-css

    Olorunbunmi Olajumoke•110
    Submitted about 1 month ago

    1 comment
View more solutions

Latest comments

  • Amiko Elvis•260
    @amikoelvis
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    I’m most proud of successfully implementing a responsive layout that seamlessly transitions from a vertical stack on mobile to a 4x2 grid on desktop, using Tailwind CSS’s utilities for Flexbox and CSS Grid. The custom mobile order (Daniel, Jonathan, Jeanette, Patrick, Kira) was a highlight, achieved by reordering the HTML and using md:order-* classes to maintain the desktop grid layout with Kira spanning two rows vertically. This required careful planning to balance mobile and desktop requirements while adhering to the style guide’s colors (e.g., bg-[hsl(263,55%,52%)]) and Barlow Semi Condensed font. The mobile-first approach, with gap-6 for spacing and px-10 py-15 for padding, ensured a polished look across screen sizes, and lazy-loading images (loading="lazy") improved performance.

    Next time, I’d focus incorporating accessibility testing (e.g., screen reader compatibility, keyboard navigation) early in the process to meet WCAG standards, and consider adding a footer for attribution to enhance professionalism.

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

    One major challenge was reordering the testimonials for mobile view (placing Kira last) while preserving the desktop grid layout, as the HTML order naturally affects the flexbox stacking but conflicts with the grid’s positioning.

    I overcame the ordering challenge by restructuring the HTML to Daniel, Jonathan, Jeanette, Patrick, Kira, and using Tailwind’s md:order-* classes (e.g., md:order-3 for Kira) to reposition cards in the desktop grid, ensuring Kira spanned two rows (md:col-span-1 md:row-span-2).

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

    I’d appreciate feedback on the following: Accessibility: Suggestions for improving WCAG compliance, such as ensuring the layout is screen-reader-friendly and fully navigable via keyboard.

    Mobile Spacing: Input on whether reintroducing max-md:mb-6 or adjusting gap-6 would enhance mobile card separation, especially on smaller screens (e.g., 320px).

    Responsive Testimonials Grid Section using Tailwind CSS

    #tailwind-css
    1
    Olorunbunmi Olajumoke•110
    @codesigner-jmk
    Posted 16 days ago

    This is nicely done.

    However, a few suggestions on my side;

    1. Code your mobile view first (especially when using Tailwind). This makes using "order" for other screens (lg and xl) easier.
    2. Gap is better used in flexbox and grid than Margin; gap will adjust to the screen size, whereas margin would maintain a fixed value of 6, making the mobile spacing look weird and unnecessarily large.
    3. If possible, try to add a screen size between your mobile and desktop; this will make the transition from desktop to mobile more seamless.

    Nevertheless, Awesome work!.

  • hamzatchiche•170
    @hamzatchiche
    Submitted 25 days ago

    responsive four-cards using tailwind

    #gsap#tailwind-css
    1
    Olorunbunmi Olajumoke•110
    @codesigner-jmk
    Posted 19 days ago

    This is nicely done; all that is needed is just a margin to the top of the page, and in between the header text, and it would be closer to perfection.

  • Ashish Kumar•150
    @0KAshish
    Submitted about 1 month ago
    What are you most proud of, and what would you do differently next time?

    I have just started learning tailwind and it is very easy to design and make responsive next time I will focus on creating well html structure.

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

    The challenges I face while using tailwind is that remembering class-names and it is important to create good html structure to apply tailwind

    Product preview card component using tailwind CSS

    #tailwind-css
    1
    Olorunbunmi Olajumoke•110
    @codesigner-jmk
    Posted about 1 month ago

    This is well done..... Nice work

  • Harsh Srivastava•40
    @Harsh-Sriv
    Submitted about 1 month ago
    What are you most proud of, and what would you do differently next time?

    The thing that i am most proud of in this is the level of similarity i was able to achieve to the provided image.

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

    The biggest problem i faced was not knowing about the pseudo-elements and had some difficulty with the grid but by searching through the web and constantly tweaking the site by going through chrome developer tools i was able to overcome it

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

    I would like to know if my code is efficient and if there are better ways to do things that i have already done

    Simple Omelet Recipe Page

    1
    Olorunbunmi Olajumoke•110
    @codesigner-jmk
    Posted about 1 month ago

    This is awesome work

  • Adeniyi Olamide Adeife•30
    @ADEIFE-17
    Submitted 2 months ago
    What are you most proud of, and what would you do differently next time?

    I am proud of what i just worked on and that is because i just started learning html and css and i was able to code this with little help.

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

    i had a problem with the media query but i was able to see through it. i also had problems with placing the container at the center of the screen, but i was also able to get through it.

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

    currently i don't think there's any but if there is i would love for anyone to notify me with the corrections. Thank you.

    A responsive social link profile using flexbox, and javascript.

    1
    Olorunbunmi Olajumoke•110
    @codesigner-jmk
    Posted about 1 month ago

    This is great work, especially considering that you used React. These are my observations and suggested corrections;

    1. Under your styles, on the container id, instead of just "margin: auto;" use "margin: 10% auto" The 10% is to give a margin to the top of the container so it doesn't stick to the top. It doesn't have to be 10%; adjust to how you see fit.

    2. Still under the container id, increase the padding; the padding for the top-bottom doesn't need to match the right-left, so instead of "padding: 10px", you can use "padding: 15px 10px"

    3. Also, remove "width: 100%" as it has no use or effect on the code.

    4. Add some padding, preferably padding top, to your P tag and h5 tag

    5. For easy coding, I would suggest using Chrome, as it allows you to inspect code, and it will also show you the parts of your code that are in works and those that are not.

    All together awesome work.

  • Congroooooo•90
    @Congroooooo
    Submitted 3 months ago

    Code & Creativity: Blog Preview Card using HTML and CSS

    2
    Olorunbunmi Olajumoke•110
    @codesigner-jmk
    Posted 3 months ago

    Hi there, this is great. I am still a relative beginner, so I can not pinpoint anything; however, I like how responsive it is.

View more comments
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