Contact Artoo Maker Lab

If you’ve spotted an error in a wiring diagram, have a project we should see, or are stuck on a build we covered, this page explains how to reach the Artoo Maker Lab editors and what to include so we can act on your message quickly.

How to Reach Us

Email is the only way to reach us. Write to contact@artoo.io and your message goes straight to the editors who write and maintain the site. Nothing is routed to a sales team, because we don’t have one.

Artoo Maker Lab is a new, independent site covering Arduino, Raspberry Pi, ESP32 and robot builds. Reader messages directly shape what we fix, test and write next, so they matter to us.

What to Send Us

Corrections

These get our attention first. A wrong pin number, a swapped resistor value or an outdated library call can cost you an afternoon or a fried board. If something in one of our guides didn’t match what happened on your bench, tell us.

Helpful details include:

  • The page title and the section or step with the problem
  • What the guide says versus what you found
  • How you confirmed it, such as a datasheet, a meter reading or a changelog

Tips and Project Ideas

Send us builds you’ve finished, techniques you’ve worked out, new boards or modules worth testing, or topics you think we’ve missed. We’re especially interested in projects that solved a real problem, used parts in an unexpected way or documented a failure honestly.

Sending a tip doesn’t guarantee coverage. Every idea we receive still helps us decide what to work on.

Questions About a Build

If you followed one of our guides and got stuck, ask. We can’t debug every project privately. Recurring questions often show us where a guide needs a clearer step, a troubleshooting section or a follow-up article.

How to Write a Message We Can Act On

Most hardware problems come down to details. A message with specifics gets a useful answer far more often than “it doesn’t work.” Include whatever applies:

Detail Example
Board and revision Arduino Uno R4 WiFi, Raspberry Pi 5 (4GB), ESP32-S3 DevKitC
Operating system or IDE version Raspberry Pi OS Bookworm, Arduino IDE 2.x, PlatformIO
Libraries and versions The exact library name and version number
Power setup USB from a laptop, a 5V 3A supply, a LiPo through a boost converter
Wiring A photo or a short pin-to-pin list
Error output The exact error text, copied rather than paraphrased
Code The smallest snippet that still shows the problem

Keep code short. A focused 20-line example is easier to read than a full project file, and building that example often reveals the bug on its own.

What Happens After You Write

The editors read every message. We reply to as many as we can. Corrections and safety issues get priority over everything else.

When a reader reports an error and we confirm it, we fix the page. If the change is significant, such as a corrected wiring step or a component swap, we note the update on the page so returning readers know something changed.

We use the details you send only to read and respond to your message. We don’t add you to a mailing list or pass your information to anyone else.

Our Position on Paid Placements

We do not accept paid placements disguised as editorial content. No company can pay to appear in a guide, to be recommended over a competitor, or to have a review written in its favour.

If we ever publish sponsored material, it will be clearly labelled as sponsored, separate from our editorial work and easy to recognise. Sending us hardware doesn’t buy coverage or a positive verdict. If we test a product, we report what we found, including the problems.

Companies are welcome to tell us about new boards, sensors, kits or tools. Send that information like any other tip, and it will be judged on whether it’s useful to our readers.

A Note on Safety Questions

We cover low-voltage electronics. Some projects touch mains power, high-current motor drivers or lithium battery packs, and email advice can’t make those safe. For anything involving household wiring or large battery systems, get help from a qualified electrician or someone who can inspect your setup in person. If you think one of our guides understates a safety risk, tell us right away. That’s a correction we want to hear about.

Thanks for Reaching Out

Every correction makes a guide more reliable for the next person who follows it, and every good question points us toward a better article. Write to contact@artoo.io when you have something to share. We read what you send and use it to make the site better.