Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
61
Comments
5

Solomon Obanijesu Philip

@Hackerbot24Nigeria1,200 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

  • A responsive space web using using Tailwind CSS

    #gsap#tailwind-css

    Solomon Obanijesu Philip•1,200
    Submitted 11 months ago

    I am open to learning.


    0 comments
  • an impressive, responsive, and feature-rich Coming Soon page

    #gsap

    Solomon Obanijesu Philip•1,200
    Submitted 12 months ago

    I am open to learning.


    0 comments
  • a stunning, responsive pricing component


    Solomon Obanijesu Philip•1,200
    Submitted 12 months ago

    I am open to learning


    0 comments
  • An advanced, fully functional e-commerce product page

    #tailwind-css

    Solomon Obanijesu Philip•1,200
    Submitted 12 months ago

    I am open to learning


    0 comments
  • a responsive and visually appealing introductory component


    Solomon Obanijesu Philip•1,200
    Submitted 12 months ago

    I am open to learning


    0 comments
  • An responsive, and interactive coming soon page for Base Apparel.


    Solomon Obanijesu Philip•1,200
    Submitted 12 months ago

    I am open to learning


    0 comments
View more solutions

Latest comments

  • Teodor Jenkler•4,040
    @TedJenkler
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    What I'm Most Proud Of: I’m most proud of learning how to use Formik for form management and Yup for validation, which streamlined the process and improved the user experience.

    What I’d Do Differently Next Time: I’d avoid deep SCSS nesting, as it can complicate the code and make it harder to manage. Simplifying the SCSS structure would lead to more maintainable and clearer styles.

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

    Challenges Encountered: I faced significant issues with SCSS nesting, which became overly complex and difficult to manage.

    How I Overcame Them: I had to rewrite parts of the SCSS code to simplify the nesting. This process taught me the importance of maintaining a flatter and more manageable SCSS structure for better maintainability and clarity.

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

    SCSS Code: I’d appreciate feedback on how to improve my SCSS code. Any tips on organizing SCSS for better maintainability and clarity would be very helpful. Best practices for writing clean and efficient SCSS would also be welcome.

    Formik & Yup Tips: I’m looking for best practices or tips on using Formik and Yup more effectively. Insights on optimizing form validation and management, as well as common pitfalls to avoid, would be greatly appreciated.

    Feel free to provide any additional suggestions that could enhance the overall quality of my project.

    Intro-component-with-sign-up-form-SCSS-Formik Public

    #react#vite#sass/scss
    1
    Solomon Obanijesu Philip•1,200
    @Hackerbot24
    Posted 12 months ago

    Nice Job Ted Keep it up it's impressive

  • Seyitan•320
    @seyifunmi00
    Submitted 12 months ago

    results-summary-component-main

    1
    Solomon Obanijesu Philip•1,200
    @Hackerbot24
    Posted 12 months ago

    @seyifunmi00 Nice Job Keep it Up, keep doing what you are doing best and also keep improving on what you are doing

  • Stanley Meruo•20
    @stanley-meruo
    Submitted 12 months ago

    VR Landing Page

    #tailwind-css
    1
    Solomon Obanijesu Philip•1,200
    @Hackerbot24
    Posted 12 months ago

    @stanley-meruo Nice Job Keep Up the Good work very impressive.

  • Adrian Trandafir 🎮•330
    @XenoMee
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    I've build this project mostly on my own. It took me 5 days but I have learned a lot from it. What I like about it is that it is very simple and straight-forward.

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

    I struggled to increase the product's quantity number in the first place, then to add the clicked product to the cart and finally to remove the item from cart.

    In the end I managed to do it all, with only a few lines of code for each challenge.

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

    Any advice or tip on how I should organize and build any React project in the future is very much appreciated !🙏

    Product List ( React, Tailwind)

    #react#tailwind-css
    1
    Solomon Obanijesu Philip•1,200
    @Hackerbot24
    Posted 12 months ago

    @XenoMee I am very impress with the Job you have done. Very Magnificent and very responsive. Keep it up man

  • Teodor Jenkler•4,040
    @TedJenkler
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    I’m proud of successfully integrating the API and Leaflet maps, even though this was a practice project with limited time investment and improving on my old project.

    I’d focus on refining the styling and addressing design inconsistencies. For now, I’ll leave it as is and start a new project this weekend.

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

    Challenges Encountered:

    One major challenge was handling environment variables for the hidden API key during deployment. Configuring them for different environments was difficult, especially with GitHub Pages.

    How I Overcame Them:

    I resolved this issue by switching to Netlify, which made managing environment variables much easier and will try learning gh pages more later.

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

    SCSS Feedback: I'd appreciate feedback on my SCSS code, particularly on how to improve styling consistency and maintainability.

    Custom Hooks/Fetch Logic: Guidance on optimizing custom hooks and fetch logic would be valuable. Any tips on improving the efficiency or structure of these would be great.

    Environment Variables on GitHub Pages: I encountered difficulties with setting up environment variables on GitHub Pages. An example or explanation on how to manage environment variables in this context would be extremely helpful.

    (I know the responsiveness is lacking and some details are missing, but given the scope of this project, I feel it’s sufficient for now.)

    IP-Address-Tracker-scss-axios-v2

    #react#sass/scss#vite#axios
    2
    Solomon Obanijesu Philip•1,200
    @Hackerbot24
    Posted 12 months ago

    @TedJenkler Nice Job and it's Magnificent but I notice that your footer was not available and the icon was not there also

    Marked as helpful

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

Mentor of the Week - 3rd Place

This badge is awarded to the 3rd placed community member on the weekly Wall of Fame.

Fun fact

The Hansen Writing Ball shown in the badge was the first commercially produced typewriter. It was put into production in 1870 with its unique ergonomic design. It was overtaken in the market in 1873 by the Sholes and Glidden typewriter which was the first keyboard to utilise the QWERTY layout we now use today.

Mentor of the Week - 1st Place

This badge is awarded to the top placed community member on the weekly Wall of Fame.

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