Browser Extensions Manager UI

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

I’m most proud of how I handled the interactivity in this project. I feel like I really leveled up my DOM manipulation and event handling skills.

If I were to do it again, I’d probably plan my component structure and naming conventions earlier, especially for the toggle switches. I ran into a few issues with repeated IDs and HTML structure that I had to refactor later. I’d also like to explore better accessibility and potentially use localStorage to persist state (like theme or filter selection).

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

One of the biggest challenges was making the toggle switches work properly. At first, I gave all the checkboxes the same id, which caused a lot of weird behavior. I had to go back, remove all the duplicate ids, and restructure the HTML to make each toggle work independently.

Another tricky part was the filter logic — figuring out how to show only active or inactive extensions based on the toggle state. It took a bit of trial and error, but I managed to get it working by looping through the cards and checking which ones were toggled on or off.

In the end, taking things step by step and testing as I went helped me solve each problem.

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

1. I’d love feedback on my SCSS structure — especially how I organized my variables, mixins, and component files. I tried to keep things modular, but I’m not sure if it’s the most efficient setup.

2. I’m curious if there’s a better way to manage the theme toggle and filters with cleaner JavaScript or maybe even using localStorage to remember state.