Contributing to FlintMinds

• Submit your own work. If you built on someone else’s design or code, say so and link to it.
• Use photos you took, or photos you have permission to share. Don’t use stock or AI-generated images as evidence of a build.
• Keep people out of the picture. Photos should show the hardware and the build, not faces, school names, addresses, or anything that identifies where someone lives or studies.
• Report results honestly. Describe what actually happened when you tested the build, including what didn’t work.

A reviewer publishes a guide only when all of this is in place and they have checked it themselves:

1. Exact hardware. The board and variant, every part with quantities, and the software versions used.
2. Real build photos. Photos of the finished build, taken by the contributor or shared with permission.
3. Wiring that matches the build. A wiring photo or diagram that shows the connections in the photos, plus written wiring instructions.
4. Complete code. Code that compiles and runs as written on the stated board, or a no-code path that was actually tested.
5. Repeatable steps and tests. Instructions someone else can follow, and a test they can run to check their build.
6. Observed results. What actually happened when the contributor ran the tests, not what should happen.
7. Known limitations. What wasn't tested, what didn't work, and where the design stops.
8. A reviewer record. A FlintMinds reviewer rebuilds the project or watches it work, checks the evidence, and records that review before publishing.

A finished form, an automated check, or a contributor’s own “it works” isn’t proof on its own. If the reviewer can’t confirm the evidence, they’ll ask for more rather than publish.

Drafts are private. When you submit, a reviewer reads the guide and checks the evidence. They may approve it, ask for specific changes, or decline it with a reason. You can follow the status and any messages in My submissions.

Reviews are done by a person, and there’s no guaranteed turnaround time. Reviewers may correct formatting or spelling in a new revision; that revision goes through the same review before anything public changes.

Published guides and builds are credited to your public username. Your email address and private name are never published.

By submitting, you allow FlintMinds to publish your approved guide or build, with its approved photos, on this website. Submitting doesn’t transfer ownership of your work to FlintMinds. We haven’t chosen a license that lets others reuse published guides outside FlintMinds.

You can withdraw a submission before it’s reviewed. Editing a published guide creates a new revision; the public version doesn’t change until that revision is approved.

FlintMinds may take down published content that turns out to be inaccurate, unsafe, or shared without permission. Old links to a removed guide show a “guide not available” page without its content.

If you delete your account, your drafts and private data are removed and published work stays up, credited to “Community builder”. See Privacy for details.

Contributor accounts are for people 13 and older. A parent, guardian, or teacher can contribute a younger builder’s project from their own account. Leave out the child’s name, face, school, and location.

Guides should list the hazards that matter for the build, such as hot tools, sharp edges, batteries, or mains power, and how to handle them. A reviewer may ask for more safety detail before publishing.