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

Awoyinka Opeyemi

@hoppYo50 points

frontEnd developer

Latest solutions

  • html and css


    Awoyinka Opeyemi•50
    Submitted 4 months ago

    1 comment
  • the use of max-width and min-height helped with the responsiveness


    Awoyinka Opeyemi•50
    Submitted 4 months ago

    0 comments
  • display: flex; justify content, width and border-radius


    Awoyinka Opeyemi•50
    Submitted 8 months ago

    width and height, must especially the resonsiveness


    1 comment
  • basic css layout display: flex;


    Awoyinka Opeyemi•50
    Submitted 8 months ago

    let's talk more on the media queries


    2 comments
  • display : flex; text-align: center;


    Awoyinka Opeyemi•50
    Submitted 8 months ago

    mobile size, especially for androids


    1 comment

Latest comments

  • budijiie•100
    @budijiie
    Submitted 4 months ago

    Product preview card

    1
    Awoyinka Opeyemi•50
    @hoppYo
    Posted 4 months ago

    good stuff

  • Nicolette Reneilwe Mashaba•140
    @Reney17
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    I am most proud of how the layout and styling of the recipe page came together. The use of semantic HTML for accessibility and the use of custom properties (CSS variables) for colors really helped maintain consistency across the design. Additionally, the responsive design works well across different screen sizes, ensuring a good user experience on both mobile and desktop.

    Next time, I would optimize the code for accessibility even more, such as adding aria-labels and alt texts to images. I would also look into further improving the SEO by adding meta tags for social media sharing and making sure the page is mobile-first to enhance the loading performance.

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

    One of the challenges I encountered was ensuring that the layout remained consistent across different screen sizes. Some of the sections, particularly the table and the image, were not aligning correctly on smaller devices. To overcome this, I used CSS media queries to adjust the layout for various screen sizes, which allowed the design to remain responsive.

    Another challenge was ensuring the styling of the list items within the ingredients and instructions sections. Initially, the default browser styling made it difficult to keep the design clean and readable. I solved this by using custom list markers, adjusting the padding, and styling the list items with specific colors and fonts to improve readability.

    Lastly, I encountered a challenge with the font sizes for headings on mobile screens. To make sure the text was still readable without being too large, I adjusted the font sizes for smaller screens using media queries and tested on multiple devices to ensure the design remained user-friendly.

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

    Accessibility Improvements: I would appreciate feedback on how to improve the accessibility of my page, especially regarding image alt attributes, aria-labels, and any other suggestions to make the page more user-friendly for those with disabilities.

    CSS Optimization: Although the layout works well, I am interested in getting feedback on whether there are any CSS performance improvements or best practices I could adopt to make the styles more efficient, especially regarding the use of media queries and CSS variables.

    SEO Enhancements: I'd like advice on SEO improvements. What are the best practices for adding meta tags for social media sharing (e.g., Open Graph, Twitter Card tags)? Also, are there any other suggestions to improve the search engine ranking of the page?

    Responsive Table Design: While the table layout works, I am curious if there are more effective ways to handle responsive tables. For example, I noticed that the table’s content might not look great on very small screens, and I’d like to know if there are more elegant solutions for making tables mobile-friendly.

    Any advice or suggestions in thes

    recipe page using html and css

    1
    Awoyinka Opeyemi•50
    @hoppYo
    Posted 4 months ago

    awesome

  • Chris•150
    @cohoc
    Submitted 8 months ago

    Social links profile

    1
    Awoyinka Opeyemi•50
    @hoppYo
    Posted 8 months ago

    great!

  • Bhavana Prabhu•80
    @prabhubhavanag
    Submitted 8 months ago
    What are you most proud of, and what would you do differently next time?

    Learnt new concepts like variable fonts, struggled a bit with grids and alignment, but was a good exercise for a beginner like me.

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

    Have I used the fonts correctly?

    Blog Preview Card Desktop version

    2
    Awoyinka Opeyemi•50
    @hoppYo
    Posted 8 months ago

    thank you as this is really helpful

  • kirankumar636164•50
    @kirankumar636164
    Submitted 8 months ago

    Blog preview card

    1
    Awoyinka Opeyemi•50
    @hoppYo
    Posted 8 months ago

    some HTML tags can't be over emphazied

  • Łukasz Gwarda•180
    @lgwarda
    Submitted 8 months ago

    QR code component

    1
    Awoyinka Opeyemi•50
    @hoppYo
    Posted 8 months ago

    all good

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