Contribution Guide

Last updated: September 15, 2026

frontendmentorsolutions.io is an open education platform that grows through volunteer contributions, like MDN and Wikipedia. Anyone can contribute by writing, reviewing, or suggesting small fixes. You don't need to be an expert: if you solved a challenge and can explain what you learned, you have something worth publishing.

The license terms for contributions are explained on the Contribution Terms page; this guide covers the practical side.

Ways to contribute

• Review and fixes: The easiest way to start. Comment under any article to report an error, suggest an improvement, or point out something missing. Feedback that shapes an article earns a "review" credit.
• Proposing an article: If there's a topic you'd like to write about, reach out at hello@frontendmentorsolutions.io with a short summary. If the topic fits, we move to the draft stage.
• Interviews: If you'd like to share your experience, you can also contribute in interview format; the process and permissions are arranged separately by email.

What makes a good article

The articles that help readers most tend to share a few traits:

• One clear focus. "How I handled the responsive layout in the Product Preview Card challenge" beats "My complete solution to the Product Preview Card challenge". A single problem, explained well, is more useful than a tour of everything.
• The reasoning, not just the result. Show the approach you tried first and why you changed it. The dead ends are often the most instructive part.
• Working, self-contained code. Code samples should run as shown. Trim them to what the point needs. Readers can see your full solution in your repo, which you're welcome to link.
• Honest scope. It's fine to say "this works for this case; I haven't tested it with X". Precision about limits makes an article more trustworthy, not less.

Good starting points if you're unsure what to write: a technique you figured out while solving a challenge, a comparison of two approaches you considered, an accessibility or performance issue you caught late, or a walkthrough of a tricky part of a specific challenge.

Proposing an article

Send a short email to hello@frontendmentorsolutions.io with:

• The topic: one or two sentences on what the article covers.
• The angle: what a reader will be able to do after reading it.
• The challenge (if applicable): which Frontend Mentor challenge it relates to.

A rough outline helps but isn't required. You'll get a reply on whether the topic fits, and any suggestions, before you invest time in a full draft.

The process

1. Proposal: Topic and a short summary.
2. Draft: You write the article; if needed, we work together on structure and sources. Markdown is preferred, but any editable format works. Drafts travel by email as well, as an attachment or a link to a doc or repo.
3. Review: The draft is reviewed before publication; we finalize it together based on the feedback. Review comments are suggestions to discuss, not one-way edits. The article stays yours.
4. Publication: The article is published with your name and profile.

Articles are managed as living documents: they continue to be updated, improved, and kept current after publication. Those who contribute to updates are added to the credits as well. If a reader's comment on your article points to something worth fixing, you're the first person we'll ask, but updates can also be made by others, with credit.

How your contributions appear

Every article credits its authors, reviewers, and contributors. Authors also get their own profile page. What you've written, reviewed, and contributed to accumulates there. Your contributions are a permanent, linkable record you can show in your portfolio.

Content principles

• Originality: Articles should be original content written for frontendmentorsolutions.io, not published elsewhere before. (Republishing on your own site afterwards is welcome, just link back to the original.) AI tools are fine as assistants, but the experience and reasoning in the article must be your own. We publish what you learned, not what a model generated.
• Code samples: Code blocks in articles are dedicated to the public domain under CC0; letting readers use code without conditions is a core principle of the platform. Only include code you're comfortable dedicating this way.
• Images: Diagrams, illustrations, and screenshots you create for your article are published under CC BY-SA 4.0, like the text; the details are on the License and Attribution page. Include only images you made yourself or have the right to share.
• Frontend Mentor materials: Do not include design files or starter code belonging to challenges; these are subject to Frontend Mentor's license terms. Share your own solution and your own explanation. Linking to a challenge's page on frontendmentor.io is fine.
• Using sources: If you drew on other sources, credit them; quotations should be short and attributed.
• Independence from sponsors: The site carries labeled sponsor placements, but no sponsored articles. Don't write to promote a product or service you have a commercial stake in; if you have such a connection to something you mention, say so in the article.

Before you submit: a quick checklist

• The article has one clear focus, and the title reflects it.
• Code samples run as shown and contain no Frontend Mentor starter code or design assets.
• Sources you drew on are credited.
• You're comfortable with the licenses: text under CC BY-SA 4.0, code under CC0, published irrevocably. (Details on the Contribution Terms page.)

Contact

For questions and suggestions: hello@frontendmentorsolutions.io