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

Responsive Browser Extensions Page

DangoDono•110
@CodingDango
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?

Proud of finishing the project in its entirety. I would definitely be more organized next time? my CSS is pretty messy, and id like to be more mindful of organizing the code and grouping them. using comments too to separate them into sections for more maintainability rather than searching for that one selector, like finding a needle in a haystack.

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

This project had many challenges. Dark mode and light mode, dealing with filtering of cards depending on their states, removing cards, reading the JSON, responsiveness, styling the checkboxes and radio buttons. all in all this project took 2 weeks in total. I was able to overcome through lots and lots of googling, the styling of the checkboxes and radio buttons I had to copy from stack overflow. I asked AI for some help and ideas on difficult topics. All in all, I used all the tools that I knew of

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

Maybe animations when removing one of the cards? they all just kind of disappear when clicked, and also, the maintainability of my CSS and Javascriptt really needs work.. and finally, it doesn't fully look like the target design, but its definitely close enough for me to call it decent. But I will be some time refactoring this

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on DangoDono's solution.

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

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.