Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 3 months ago

Browser extensions Filter mune (☕)

accessibility, animation, sass/scss, typescript, bem
Ezequiel•1,250
@3eze3
A solution to the Browser extension manager UI challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

What are you most proud of, and what would you do differently next time? 🌟 Hello community! My name is Ezequiel, and I’m excited to share my solution for this challenge. 🍟

🔧 I built this project using the following tools and techniques:

✅ HTML5: For a solid structure and ensuring the accessibility of the site. 🏗️ ✅ CSS3/SCSS: For styling and bringing each element to life. 🎨 ✅ Ts: To handle the calculator logic and theme switching dynamically. ✅ Strict BEM Notation: Ensuring clean, organized, and maintainable code. 💼 ✅ Responsive Design: Optimized from the ground up for an optimal experience on all devices, from mobile to desktop. 📱💻 ✅ Dynamic Theme Management with SASS: Efficiently switching themes without redundant code.

If you have any feedback or suggestions for improvement, I would greatly appreciate it if you could share them in the comments. Constructive feedback is always valuable for growth! 😊

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

If you have any feedback or suggestions for improvement, I would greatly appreciate it if you could share them in the comments. Constructive feedback is always valuable for growth! 😊

I hope this solution inspires and motivates others to keep learning and improving! 🚀✨

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Joshua Adediran•160
    @Challmejosh
    Posted 3 months ago

    Nice i love the animation especially on the theme toggle button. The active toggle slide isn't work i think you should do that

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!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub