All solutions

What are you most proud of, and what would you do differently next time?

I'm proud of my eagerness to improve with each challenge, especially in terms of organization. I'm looking forward to refining it even more next time.

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

The required items to complete this task were not a problem. However, a challenging aspect of the task is organizing everything in a way that is clear to everyone while also preparing for the potential growth of the website.

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

Despite being satisfied with my progress, I still believe that the code can be organized even better. For instance, by splitting it into smaller components, using clearer BEM naming conventions, and implementing other simplifications.

What are you most proud of, and what would you do differently next time?

Compared to my previous projects, this project help me understand semantic HTML even more. Also, helped me understand how to create better reusable components in React.

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

Despite this challenge of having only one card, in order to create an accurate layout, we need to think in advance about the following cards that can be applied in the future.

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

I'm striving to make less code but to be reusable. Also, to increase readability and accessibility.

What are you most proud of, and what would you do differently next time?

With every project I work on, I strive to create readable and well-organized code. In this particular project, I used Angular to break the code into components.

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

The most challenging part is finding the right connection between elements to determine what should be created as a component and how that component should look. For example, it's not enough to create a button component based on a single instance. The goal is to create a shared structure that can be used for all, or multiple, buttons—while the content can vary.

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

As mentioned before, I'm aiming to create the best relationships between elements. Additionally, I want to improve the organization of my SASS, such as writing more efficient mixins.

Since I want just a quarter of circles in the corners to be shown, I used html, body { overflow: hidden; } It is fine, unless you try to zoom page, then you can't see full card. Every suggestion for the solution will be appreciated!

I'm intrested, since I've done this challenge with webpack, are @forward and @use valid? It didn't work for me, but @import does. In addition, any suggestion for better SASS organization will be helpful.

Since I want this project to be responsive, how I need to work with font-size? If someone use ex. font-size: 50px in the browser settings, how the text will follow other elements on the page (ex. its parent). Should I use functions like clamp, calc, media query or something else? Is it fair to use limit such as 50px even if you choose font-size 72px?