About

frontendmentorsolutions.io is an open education platform about web development, built around Frontend Mentor challenges. Both our own team and community contributors share their approaches and explain the reasoning behind them. Like MDN and Wikipedia, the platform is volunteer-driven and openly licensed: anyone can contribute, and everyone is free to use what's published here.

What you'll find here

You won't find official or complete solutions on this site. Official solutions don't exist for Frontend Mentor challenges at all, and that's by design: the point of the challenges is to solve them yourself and improve through feedback.

What you will find is the next best thing: the common issues that come up in each challenge, how to fix them, and modern approaches worth knowing. Think of it as collective feedback. If you've solved a challenge, check the common issues for it and use them to upgrade your own solution.

Relationship with Frontend Mentor

This is an independent, community-run project, not affiliated with or operated by Frontend Mentor, though it runs with the kind permission of Matt, Frontend Mentor's founder. The "Frontend Mentor" name and brand belong to them, and challenge materials (design files, style guides, starter code) remain under Frontend Mentor's own license terms.

Special thanks to Matt for building the wonderful Frontend Mentor platform, and to the community team on Discord for patiently answering our endless questions.

Who's behind this

The site is created and maintained by Alper and James.

Why an open platform?

Solutions to a challenge end up scattered across repos, comment threads, and chat histories, and the feedback that made them better usually disappears with them. An open platform keeps that collective knowledge in one place, under licenses that let anyone use it, improve it, and build on it. The work of explaining something well should only have to happen once.

In practice, openness means:

• Open content. All text is licensed under CC BY-SA 4.0. You can share it, adapt it, and use it commercially, as long as you give credit and share alike. Code samples go further: they're dedicated to the public domain under CC0, with no conditions at all.
• Credit that lasts. Copyright stays with authors, and every article lists its authors, reviewers, and contributors. Your contributions build a permanent, linkable record you can point to from your portfolio.
• No paywalls. The site is funded by directly sold sponsorship and advertising and by voluntary reader support, never by locking up content. Support is always optional: the content stays free and openly licensed either way.
• Sponsors don't touch the content. The site and the newsletter may carry sponsor placements and ads, sold directly by us and always labeled. There are no sponsored articles, sponsors have no say in what gets written or published, and no advertising network is involved.
• No ad tracking. No tracking or profiling cookies, no advertising networks, no third-party tracking scripts, and your data is never shared for advertising: sponsors receive aggregate figures only. Visitors who aren't signed in receive no cookies at all, and visit statistics are collected with a first-party, cookie-free system: anonymous for visitors, linked to the account for signed-in members, as the Privacy Policy explains.
• Minimal data. Sign-in works via magic link (no passwords are stored) and membership data is kept to the minimum needed to run the site.

We didn't invent this model; we adopted it from the projects that proved it works. Our License and Attribution page is itself adapted from MDN's licensing page, which is exactly the kind of reuse these licenses exist for.

Accessibility

We want this site to work for everyone: keyboard users, screen reader users, and anyone who tunes their browser to their needs. The theme is built on semantic HTML, follows your system's light/dark and reduced-motion preferences, offers adjustable text size, and keeps all content readable without JavaScript. Accessibility is also part of what we teach, so we try to hold our own pages to the standard our articles preach. If you hit a barrier anywhere, email hello@frontendmentorsolutions.io. We treat accessibility problems as bugs.

Questions?

The FAQ covers the common ones. For anything else, email hello@frontendmentorsolutions.io, or use the Contact page.