All solutions

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

I guess , I realized how structured I can be when it comes to create a project step by step and following a plan. Starting with the HTLM structure then CSS and finally implementing the JavaScript logic maded easier to create the FAQ. However, next time, I will revise position CSS property prior to styling because I lost time figuring out what was the problem with the responsive aspect of the project.

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

At first, my positionning was not correct. I used the "position: absolute" property on my "container" element and after that "position: absolute" for the "faq-container" element and the "attribution" element. Because of that, the layout was not responsive. By using only relative positionning, flexbox layout and the property z-index, I managed to ensure a solid layout for all screen sizes. This project also reinforced the importance of maintaining a balance between design aesthetics and functionality, ensuring that the interface is both visually appealing and user-friendly.

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

Learning a new language is always challenging but also rewarding. For this project I wanted to start my initiation with TypeScript and it went very well. I learned the basics for now, but I can see now why it is so useful. It makes your code more robust and enforces safer coding practices.

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

The real challenge I had for this project was about the button, advice ID and advice text elements that were marked as "possibly null" by TypeScript although these elements were find in the DOM when only using JavaScript. Even if my JavaScript code was working perfectly, TypeScript's goal is to make sure our code is stable and handles all potential edge cases, including the possibility of elements not being found in the DOM.

Because I was sure my element will never be "null" I added the non-null assertion operator (!). I found this solution on the TypeScript documention.