Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 14 days ago

Grid - JS - HTML

Mayza•40
@MayzaMendesRodrigues
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?

I'm proud to have implemented a JavaScript cloning and templating approach that improves code security and structure. It made the UI safer and the code more modular and maintainable. Next time, I would focus on applying filters that modify the data directly in the JSON, rather than just updating the visual interface. I’d also like to integrate a frontend framework like React to make the application more scalable and organized.

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

This project helped reinforce what I’ve been learning so far. The main challenge was applying concepts I had studied across different platforms and putting them into practice. To overcome this, I broke the project into smaller tasks, reviewed documentation regularly, and tested each part of the UI as I built it.

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

I’d appreciate feedback on how to better handle filters that modify the JSON data itself, rather than just the UI. I'm also open to any suggestions or improvements from the community — I'm here to learn and grow from others’ experiences.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,410
    @thisisharsh7
    Posted 14 days ago

    Excellent work overall! Your use of JavaScript templating and cloning is impressive, enhancing security and modularity.

    • For improvements, consider modifying the JSON data directly for filtering. You could update the extension array using methods like map or splice when toggling isActive or removing items, ensuring data and UI stay in sync.

    • For scalability, integrating React could streamline state management—look into hooks like useState for managing extensions. The filter buttons work well, but adding a loading state during fetch could improve UX.

    • Accessibility can be enhanced by adding ARIA attributes (e.g., aria-checked on toggles) and keyboard navigation for buttons.

    • To optimize, consolidate repeated CSS properties (e.g., border-radius) into a shared class and use CSS variables for colors consistently.

    • Next steps: explore state management libraries (e.g., Redux) or CSS-in-JS for larger projects.

    Great job overall-keep up the good work!

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