All solutions

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

It's my first time animating stuff with CSS. At first, I wanted to use Odometerjs for the number animation, but after some research, it seems that I could implement it easily. Overall, I'm happy how the animation turned out (maybe it's a bit too fast?), but next time I'll consider using a library instead.

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

• I discovered the STATUS_ACCESS_VIOLATION error on Chrome. My custom CSS property was the issue. So I reduced the duration of the transition + replaced counter-reset with counter-set. It seems that it fixed the issue, but I'm not sure. At least my browser haven't crashed ever since.

• To compute the difference between two dates, I wanted to go with an accurate solution (taking into account leap years and so on). In the end, out of laziness my own solution wasn't accurate and had a lot of approximation. So I ended up using a library for this task, since it was errorless, but easy to integrate.

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

• If anyone has an idea on how to compute the diff between two dates accurately without a library, I'm eager to know!
• I'm still unsure about my animation. I'm afraid it may crash my browser again.
• Does anyone have any suggestions on how I should organize my CSS (especially with TailwindCSS) & structure my components?

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

I wanted to apply what I read on d3.js for data visualization on a simple project. So this challenge helped me learn the basics.

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

• It was my first time deploying a vanilla html + css + js on Vercel, and it didn't go smoothly. It took me awhile to get it working. It was mostly due to my lack of understanding of the basics, especially how to serve static files directly.
• Styling and placing stuff on the svg by hand + adding interactiveness with d3.js was not fun.

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

I realize how much I prefer vanilla CSS over TailwindCSS.

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

• It was easier than I thought to format the amount's input without using a third-party library. But it led to accessibility issues mostly on mobile (the input is no longer of type number, but text). Next time I'll probably use a library like Cleave.js so I won't have to deal with all the side effects.
• I'm happy I got the opportunity to experiment with Zod for client-side data validation (even if it was probably overkill here, but it made error handling way easier and much more flexible).
• I tried experimenting with CSS grid for mobile responsiveness.

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

• I struggled so much on changing the color of the radio buttons. It seems that I can't change it directly, since it is browser dependant (?). I had to make it invisible and replace it with 2 divs placed one inside another with absolute positioning, which resulted in slightly different layout with different browsers/screens. Next time I'll probably use an image instead. Any advice is much appreciated.
• I'm still having trouble with the content of my page wrapping along the vertical axis on small width, and overflowing its container (I can't find a way to crop the content when I reduce the width).
• I couldn't expand the background of the result's section to match full remaining height, so it poses an issue on large vertical screens.

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

Not much to say about this one

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

Couldn't manage to use CSS only. My CSS-only solution resulted in a bad layout: the title of the question, the checkbox input and the answer were rendered on the same line. This is because to conditionally render my tag (with the answer) based on the "checked" value of the input, they had to be siblings at least. Or, that's what I read. So I had to resort to JS, unfortunately. :'(

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

So, I'm finally starting my webdev journey. What I'm not proud of is that it took me way too long to achieve this challenge, more or less. But I'm happy that I took enough time to do research, and try to really grasp what I was doing. Yeah I know.. using NextJS is probably overkill here, but I want to learn how to use this framework, so I'm glad I did!

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

It's my first time doing responsive design, and my first attempt at really trying to organize as much as possible my html page, so I had to google a lot of stuff.

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

It's a bit unfortunate that I couldn't make the page look right with super low width ( tag... Also, due to me flex-wrapping words, the text is unreadable at such dimensions. Finally the article gets resized and the beige background becomes visible again. If anyone has any suggestions, I would be very thankful!