Editorial Process

Who's responsible

Every guide on My Morse Code Translator is edited and signed off by Sukie, the creator of the site. One person, one consistent voice, one point of accountability. If a page has a mistake, it's hers to fix — and she wants to hear about it via the contact page.

How AI fits in — and where it stops

I'll be upfront, because you deserve to know: I use AI as a research assistant and first-draft tool. It's great for gathering background, suggesting an outline, and getting words onto the page so I'm not staring at a blank screen. What AI is not allowed to do here is publish. No article goes live as raw AI output.

After a draft exists, I edit it by hand — rewriting for my own voice, cutting the generic filler that AI tends to produce, adding real examples and the small first-hand observations that only come from actually using the tool, and correcting anything that's vague or wrong. The goal is that every page contains something a machine couldn't have produced on its own: a specific detail, a lived mistake, a genuinely useful shortcut. In short, AI drafts; a human decides, edits, and takes responsibility.

The accuracy commitment

Morse code is a precise system, so I hold the guides to a precise standard. The dot-and-dash patterns, the timing ratios between dots, dashes, and gaps, and the letter and word spacing all follow the ITU-R M.1677 international Morse code standard — the same reference used by radio operators worldwide. When I describe how a letter sounds or how fast a message plays, it's measured against that standard, not guessed at.

For anything historical or technical beyond the core code — how Morse developed, how it's used in amateur radio, how it shows up in music or film — I check against reputable references such as the relevant Wikipedia articles and organizations like the ARRL for ham-radio specifics, and I try to name those sources in the text so you can follow the trail yourself.

Keeping pages current

Guides aren't written once and forgotten. When I add a feature, spot an error, or get a good correction from a reader, I revise the relevant page and update its “last updated” date to reflect the real change — not an automatic timestamp that moves every time the site rebuilds. If a date says a page changed, the page actually changed.

Corrections welcome

If you find something inaccurate, outdated, or just unclear, please tell me through the contact page. Corrections get priority, because a Morse guide that's subtly wrong is worse than no guide at all. For the rest of the story behind the site, the about page has it, and the privacy policy covers how your data is handled.