Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
15
Comments
15
P
Joel Eguiza
@joeleg96

All comments

  • P
    JConan•90
    @JConan
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    I successfully wrote tests in the TDD style, which have been invaluable during redesigns. Next time, I would aim to iterate faster on the test-design cycle to further enhance the process.

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

    When adding AI to the system, the reactivity code didn't behave as expected. I identified the issue and corrected it, ensuring functionality, although the solution might not be the most optimal.

    using sveltekit with static site + test

    #svelte#vitest
    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 26 days ago

    Hey JConan,

    Overall good job on your solution, it looks very clean, and works very well. There are a few small details that you could fix though:

    1. I don't think you're using the correct font in the starting menu.

    2. I noticed that when you start a new round in both vs cpu and PVP X no longer goes first.

    3. I think it might be helpful to apply a delay to the CPU's turn rather than it going automatically, but this might just be a personal preference.

    This is just me nit picking for constructive criticism though. Great job on a great solution, and good luck on your coding journey!

  • anjali-sharma90•150
    @anjali-sharma90
    Submitted about 1 year ago

    BMI Calculator using HTML, SCSS, JS

    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted about 2 months ago

    Hey Anjali,

    Good job on this solution. The design is clean and responsive, with no awkwardness when resizing the screen. The javascript seems to work, even though I only tried one set of numbers, but it displays the correct BMI and weight range.

    There are a few differences in the aesthetics of your solution when compared to the actual design, but your solution still looks very clean and professional. Other than that great job on this project, and good luck on your coding journey!

  • bambino•340
    @Bambino143
    Submitted 12 months ago
    What challenges did you encounter, and how did you overcome them?

    Working with JavaScript was a bit challenging, I think I wrote more code than necessary.

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

    How can I improve my skills in creating responsive web designs? I'm currently not very confident in this area. Should I start building with a mobile-first approach? Any advice would be greatly appreciated.

    Responsive e-commerce page

    #jquery
    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 2 months ago

    Hey Bambino,

    Overall good job on your solution. Good job on the spotlight and getting the shopping cart to work!

    Some constructive feedback:

    1. They layouts based off of screen size don't completely follow the designs provided. For example, for tablet the thumbnails shouldn't be displayed.
    2. Your break points could be adjusted a bit, because at some point the "Add to cart" button is partially off-screen.
    3. When the screen is in the mobile screen size, the "Add to cart" button needs some margin on the bottom so that it isn't so close to the bottom of the browser.
    4. The burger-menu doesn't show up at any point, so the menu options become inaccessible past a certain screen size.

    Overall, great job on this project. You got the image gallery and shopping cart to work which is really the hard part of the project. Keep up the good work and good luck on your coding journey!

  • Yacoub AlDweik•3,540
    @YacoubDweik
    Submitted 7 months ago

    News homepage

    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 2 months ago

    Hey Yacoub,

    Overall your design looks good, but I noticed that when you adjust the screen size the side-bar menu randomly shifts to the side without it being interacted with. The side-bar menu should only appear when you click on the hamburger, but I noticed it appeared on my screen when changing screen sizes.

    Other than that I think you have a good solution.

    Marked as helpful
  • Tonny Blair•470
    @Tonny-Blair-Daniel
    Submitted 4 months ago

    Contact Form

    #jquery
    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 2 months ago

    Hey Tony,

    Overall great job on this solution! The javascript works flawlessly, which is the hard part of the project, so congrats on that!

    Some tiny things that you could improve:

    1. There are a bit of stylings that you didn't implement into your solution: button fill colors, text border colors, text border color error states.

    2. In your Javascript I would include an eventlistener to check for clicking in the query type containers so that they are also selected in those scenarios (it makes it a bit inconvenient that it only works on the button itself or on the text).

    Other than that great job, and good luck on your coding journey!

    Marked as helpful
  • EmicJoykiller•270
    @EmicJoykiller
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    I'm most proud of how clean and consistent the FAQ Accordion turned out, especially the responsive design and the smooth toggling behavior for opening and closing answers. It was really satisfying to ensure the icons switched correctly between plus and minus, and that everything stayed accessible and visually balanced across different screen sizes.

    Next time, I would focus more on adding small transition animations (like a smooth slide down/up effect when answers open and close) to make the experience feel even more polished. I’d also organize my JavaScript a bit more modularly for easier scalability if I wanted to add more FAQs dynamically.

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

    One big challenge was controlling the visibility of the answers and synchronizing the icon changes (from plus to minus) without using a "toggle" icon by default. Instead, each question had its own static image, so I needed to manually switch the src attribute of the images depending on the FAQ item's open/close state.

    Another challenge was making sure the first FAQ item didn’t show an unnecessary top border. Initially, using :first-child and :first-of-type didn't fully solve the issue because of how the layout was structured, but with careful CSS targeting and structure adjustments, I was able to fix it cleanly.

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

    I would love feedback on two things:

    How to best add smooth open/close animations to the answer sections without causing layout shifts or performance issues.

    If there are more efficient or scalable ways to structure the JavaScript, especially if I wanted to make the FAQ list dynamic in the future (like fetching questions/answers from a JSON file instead of hardcoding them in HTML).

    FAQ-accordion

    #accessibility#animation#jquery#pure-css
    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 3 months ago

    Hey Emic,

    Great job on your solution. Overall it looks great, and your code looks very streamlined. I found it interesting that when you clicked to show the answer, your container expanded up rather than down. Not quite sure why, but it differed from how mine responded, so I just found it interesting.

    Great job on your solution and I wish you luck on your coding journey!

  • alexpeteronoja•280
    @alexpeteronoja
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    Being able to complete this project.

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

    understanding the ARIA (Accessible Rich Internet Applications). But I was able to learn about them in this project.

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

    Please reveiw this code and please tell me how I can improve and follow best practices.

    Interactive Rating Component

    #bootstrap#jquery
    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 3 months ago

    Hey Alex,

    Great job on you solution! Your javascript works flawlessly. The only minor changes that I would make are:

    1. Your star icon and (1) button look a little smushed. This should be an easy fix with CSS.
    2. I could be wrong on this one, but I believe the hover color is white, and the clicked color is orange for the rating buttons.
    3. Lastly, the background color for the buttons should be a lighter shade of gray.

    I'm really nit picking here for some constructive feedback, but honestly great job!! Keep up the awesome work and good luck on your coding journey!

  • P
    Andre Dantas•240
    @andredantasti
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    Me Orgulho de estar aprendendo a trabalhar com flexbox, mudaria em não utilizar tanto a tag de margin no css, na hora de responsividade da mais retrabalho;

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

    desafios de colocar a imagem de fundo e uma cor opaca, tive que recorrer a IA para me dá uma luz;

    Meet landing page solution - Responsive Andredantasti

    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 3 months ago

    Hey Andre, it looks like your solution is having some responsiveness issues. I tried resizing you solution, and at some point it breaks and thing's are no longer aligned. You might want to check your CSS and see if what the issue is. It might be as simple as adding a margin-left: auto; and margin-right: auto; to make sure that your content is keeping itself centered as your window size changes. I also noticed that your mobile design doesn't change the collage section and it overflows on the x axis. You can set display: grid on the container and then assign each image a part of the grid using grid-area. I hope this helps some! Keep up the good work and good luck on your coding journey!

    Marked as helpful
  • ThariqRamadhan101•150
    @ThariqRamadhan101
    Submitted 3 months ago
    What are you most proud of, and what would you do differently next time?

    Learn about BEM and Grid

    Testimonials grid section

    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 3 months ago

    It looks like your solution follows the design provided, and that you have a good grasp of grid. I did notice however, that you forgot to include a media query for the tablet design. Another minor thing I noticed was that your column and row gaps are significantly smaller than those of the design, so it makes your solution a little cluttered, and it could breathe a bit more. Other than that great job, and good luck on your coding journey!

  • P
    AnjelToppo•590
    @AnjelToppo
    Submitted 4 months ago

    Four card feature section

    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 4 months ago

    One thing that I would recommend, in order to make your code more condensed, is to give all the cards a common class name since they all have certain features in common: size, box shadow, margin, etc that way you don't have to give each individual card those css attributes. You can also give them unique class names, like the supervisor card "cyan" and the team builder card "red" that way you can target the border and change the color to it's respective color. Another thing, though this might just be me and I'm not sure if it's correct or not - but I feel like your webpage, though it transitions to the correct layouts, has a lot of things that are moving around, and it visually makes the page "confusing." For example, in the mobile layout, if you start to resize the page the title moves all over the place, and I feel like that just makes the transitions look a little clumsy. Again, maybe this is just me. Overall I think you did a great job in implementing each layout! Great job and good luck on your coding journey!

  • sherimin•380
    @sherimin
    Submitted 10 months ago

    Product preview card component

    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 4 months ago

    I took a quick look at your code and design, and it seems to be responsive to changes in screen size, so great job on that. One change that I would make is to make a media query for the hover state since this shouldn't be applying to mobile sizes or tablet sizes, since there wouldn't be a cursor at those screen sizes. Other than that great job, and good luck on your coding journey!

  • Joan-Bell-Faye•100
    @Joan-Bell-Faye
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    Owww that was a headache! Next time I would use a text_wrapper div

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

    Styling the bullet points. I learned how to use li::marker to style these and also list-style-position: outside; to keep the list item text aligned with itself rather than the list marker.

    When I wanted to make the page responsive I realised that I should have checked the mobile and desktop designs more thoroughly as the padding around the image that was contained in the card div created a problem. I then had to go back and add another wrapper div around the text so that I could remove the padding from the card and have some padding on the text. It was a PAIN.

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

    One of the main issues I struggled with was identifying the colours as the changes between these were to subtle. Any pointers on this for consistency moving forward, or anything else you notice I am happy to receive feedback on. :)

    Responsive recipe page with media queries and many colours

    2
    P
    Joel Eguiza•350
    @joeleg96
    Posted 4 months ago

    It looks like your live page isn't actually working, so I wasn't able to take a look at your work to see how it looks/responds to page sizes. I took a quick look at your code though and I like that you used variables to define your font sizes and the various font colors. This makes it a lot easier to make those changes rather than assign them individually. I noticed you switch a lot between viewport w/h, rem, and pixels throughout your code. I would try and stick to one so that it's easier for your to make the necessary changes, rather than cycling through various measuring standards. It would be like an engineer switching between yards, meters, feet, and kilometers without any clear reason. Overall keep up the good work and good luck on your coding journey!

    Marked as helpful
  • P
    Paul Wonka•260
    @pdoubleu30
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    I'm most proud of putting my head down and working through this project. My HTML and CSS skills are still very basic, but I feel that I am learning and growing.

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

    I had challenges with the hover aspects of the project, but it was fun to work through it.

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

    I would like help with the focus aspects of the project. Thank you!

    html & css

    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 4 months ago

    Overall your solution looks like the design that was provided. One thing that I found interesting about your code was that you used "li" along with anchor tags when doing the media section. Another solution, which is the way that I did it, could be to use the button element in your HTML, and put all of the buttons inside of a container div. Then in your CSS you could display: flex; and flex-direction: column; that way you can get them to stack up vertically. Just another possible way to tackle to same problem. Hope this helps, and good luck with your future coding projects!

    Marked as helpful
  • Fehmidatanzeel•570
    @Fehmidatanzeel
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    I am most proud of successfully implementing a responsive design using only HTML and CSS. It was a great learning experience to structure the layout properly and style it effectively. Next time, I would focus more on improving accessibility and adding small animations to enhance user experience.

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

    One challenge I faced was aligning the content properly within the columns while keeping the design responsive. Initially, the layout was breaking on smaller screens. I solved this issue by using CSS Flexbox and Media Queries to ensure a smooth and adaptable design.

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

    Through this challenge, I learned how to structure content effectively using HTML and apply modern CSS techniques to create a visually appealing layout. Additionally, I improved my skills in handling responsive design and debugging layout issues.

    blog previw card

    1
    P
    Joel Eguiza•350
    @joeleg96
    Posted 4 months ago

    I checked your designs using various screen sizes and it seems to respond well to those changes, so great job on implementing a working solution to a problem that you were initially having. Keep up the great work and good luck on your programming journey!

  • Matheus Quintanilha•30
    @MatheusQuintanilhaa
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time? Solution Retrospective

    1. What are you most proud of?

    I am most proud of successfully implementing a responsive design that adapts seamlessly to various screen sizes, from mobile devices to large monitors. The use of media queries and relative units like percentages and rem allowed me to create a flexible layout without compromising the user experience. Additionally, I was able to maintain the original code structure while adding responsiveness, which shows my ability to work with existing codebases.

    2. What would you do differently next time?

    Next time, I would focus more on optimizing the performance of the project, especially for mobile devices. For example, I could explore using CSS Grid for more complex layouts or optimizing image sizes to reduce loading times. I would also consider adding more interactive elements, such as animations or hover effects, to enhance the user experience.

    3. Where do you need support?

    I would appreciate feedback on how to further improve the accessibility of the project, such as ensuring proper contrast ratios and screen reader compatibility. Additionally, I would like to learn more about advanced CSS techniques, like using clip-path or mask-image, to create more visually appealing designs.

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

    1. Responsive Design

    • Challenge: Ensuring the layout looked good on both mobile and tablet screens was initially challenging, especially with fixed dimensions in the original design.
    • Solution: I used media queries to adjust the layout for different screen sizes. For mobile devices, I switched to relative units like percentages for widths and padding, which made the design more flexible. For tablets, I increased font sizes and adjusted container widths to better utilize the available space.

    2. Text Alignment and Line Breaks

    • Challenge: The text wasn't breaking correctly on smaller screens, and the alignment didn't match the design in some cases.
    • Solution: I used <br> tags to control line breaks in the HTML and adjusted the line-height and text-align properties in the CSS to ensure the text was properly aligned and readable on all devices.

    3. Maintaining Code Consistency

    • Challenge: Adding responsiveness without altering the original code structure was tricky, as I wanted to keep the code clean and maintainable.
    • Solution: I kept the original CSS intact and added media queries at the end of the file. This approach allowed me to introduce responsiveness without disrupting the existing styles.

    4. Testing Across Devices

    • Challenge: Testing the design on multiple devices and screen sizes to ensure consistency was time-consuming.
    • Solution: I used browser developer tools (like Chrome DevTools) to simulate different screen sizes and made adjustments based on the results. This helped me quickly identify and fix issues without needing physical devices.

    5. Performance Optimization

    • Challenge: I was concerned about the performance of the QR code image on slower networks or devices.
    • Solution: Although I didn't implement it in this project, I researched using responsive images with srcset to serve optimized images based on the device's screen size and resolution. This is something I plan to implement in future projects.
    What specific areas of your project would you like help with? Challenges and Solutions

    1. Responsive Design

    • Challenge: Ensuring the layout looked good on both mobile and tablet screens was initially challenging, especially with fixed dimensions in the original design.
    • Solution: I used media queries to adjust the layout for different screen sizes. For mobile devices, I switched to relative units like percentages for widths and padding, which made the design more flexible. For tablets, I increased font sizes and adjusted container widths to better utilize the available space.

    2. Text Alignment and Line Breaks

    • Challenge: The text wasn't breaking correctly on smaller screens, and the alignment didn't match the design in some cases.
    • Solution: I used <br> tags to control line breaks in the HTML and adjusted the line-height and text-align properties in the CSS to ensure the text was properly aligned and readable on all devices.

    3. Maintaining Code Consistency

    • Challenge: Adding responsiveness without altering the original code structure was tricky, as I wanted to keep the code clean and maintainable.
    • Solution: I kept the original CSS intact and added media queries at the end of the file. This approach allowed me to introduce responsiveness without disrupting the existing styles.

    4. Testing Across Devices

    • Challenge: Testing the design on multiple devices and screen sizes to ensure consistency was time-consuming.
    • Solution: I used browser developer tools (like Chrome DevTools) to simulate different screen sizes and made adjustments based on the results. This helped me quickly identify and fix issues without needing physical devices.

    5. Performance Optimization

    • Challenge: I was concerned about the performance of the QR code image on slower networks or devices.
    • Solution: Although I didn't implement it in this project, I researched using responsive images with srcset to serve optimized images based on the device's screen size and resolution. This is something I plan to implement in future projects.

    Responsive QR Code Challenge

    2
    P
    Joel Eguiza•350
    @joeleg96
    Posted 4 months ago

    You did a great job of using media queries to ensure that the design was responsive to various screen sizes. The design transitioned seamlessly across various screen sizes. Great job, and I wish you good luck on your Coding Journey.

    Marked as helpful
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

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