What are you most proud of, and what would you do differently next time?
I feel like my use of Flexbox and media queries improved, and figured out how media queries cascade/override one another based on the screen size satisfying certain conditions. Overall happy with the result here, I could have spent more time tweaking the font spacing/size, element padding and margins, etc to get it more true to the original design but I mostly wanted to work to the spirit of the challenge rather than spend a bunch of time getting it 'perfect'.
What challenges did you encounter, and how did you overcome them?
Not a challenge per se, but I was thinking I maybe could have used the vh and vw values to adjust the size of elements so it would be more dynamically responsive to screen size changes, rather than just hardcoding 3 different sizes. I was thinking maybe clamp() would be the way to go about this, so I could keep the values within a reasonable range, but also not have to hardcode values for multiple media queries.
What specific areas of your project would you like help with?
See above, I'm open to suggestions on how to achieve a more dynamic solution for styling responsiveness.
What are you most proud of, and what would you do differently next time?
This project was builded to learning sass, using sass with BEM methodology give me the chance to improve and expand my knowledge over so many tools made for frontend development.
What are you most proud of, and what would you do differently next time?
more and more used to it. I'll sketch the layout earlier so that I don't have to be confused later in the process.
What challenges did you encounter, and how did you overcome them?
mainly the mobile part, I have to figure out how to make the layout specific to the mobile layout. Later, I found the answer to use @media although I wonder if it is the right way to do.
What specific areas of your project would you like help with?
please point out more about how I can make it better. Thanks.
What are you most proud of, and what would you do differently next time?
That I was able to complete this on my own. One thing I would do differently next time is leaving comments in my code to know what does what so i don't forget or I can use it again in the futrue.
What challenges did you encounter, and how did you overcome them?
I had a hard time centering my main container in the middle. i was able to find online resources to help me out.
What specific areas of your project would you like help with?
I do not know how media queries work so i was unable to complete the task for the mobile. I needed help spacing my "th" and "td" in my table to create more space between them, i tried many things but and searched online but I couldn't find anything that helped me. I would also like to learn more on how to center better your content.
What are you most proud of, and what would you do differently next time?
During this challenge, I learned that a parent flex box could not be centred. However, I also learned that you could center a child flex box inside a parent flexbox to create a centred box along the vw/vh.
I enjoyed the simplicity yet the challenge of figuring out this exercise.
What challenges did you encounter, and how did you overcome them?
It took about three hours of playing with Bootstrap and CSS before I realized I needed a flex-parent and then a flex-child to center.
I also never knew I could 100vh the parent and justify/align the flex-child.
I also wanted to try to do this in Bootstrap but couldn't. I'm finding HTML/CSS easier than Bootstrap.
What specific areas of your project would you like help with?
I'd love to learn more about Bootstrap! While it's great for certain areas of a website, I also find CSS easier in other areas. If possible, I'd love to figure out a way to combine the two, as Bootstrap buttons are easier to configure.
What are you most proud of, and what would you do differently next time?
I already have experience with APIs, so I used this challenge to test this platform and see how it works. To make the challenge more interesting for me, I added some extra features, such as a spinning animation to the button when it's clicked, a toast component that appears when the API is on cooldown to avoid it being mistaken by a front-end issue. I also added a toggle component that allows the user to disable the toast notifications. The user's choice is saved in the local storage, so it persists even after the user refreshes the page.
What challenges did you encounter, and how did you overcome them?
I always forget how to make the toggle work, so I have to check W3Schools every time.
What specific areas of your project would you like help with?
What are you most proud of, and what would you do differently next time?
Was able to complete the challenge relatively quickly using Tailwind and rapid prototyping.
What challenges did you encounter, and how did you overcome them?
Adding hover state required a better use of elements. Initially was using a button, but changed to an anchor tag to be styled like a button which is more semantic.
What specific areas of your project would you like help with?
Any additional recommended effects or Tailwind efficiencies would be appreciated!
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!