Editorial Guidelines
Clear, consistent writing helps readers find and understand information. These guidelines ensure content across the site feels cohesive, regardless of who wrote it.
We follow the Associated Press Stylebook (AP Style) as our primary reference. AP Style is the standard for news organizations and technical publications because it's clear, concise, and widely understood. When this guide doesn't cover something, defer to AP Style.
Voice and tone
Write as if you're explaining something to a fellow amateur radio operator at a club meeting. Be helpful, direct, and respectful of the reader's time.
Be direct
Say what you mean. Avoid hedging, filler words, and unnecessary qualifiers. "Connect the antenna" not "You might want to consider connecting the antenna."
Be inclusive
Assume readers have varied backgrounds. Explain jargon when first used. Don't assume everyone knows what CTCSS means.
Be practical
Focus on what readers can do with the information. Include examples, expected outcomes, and troubleshooting tips.
Active voice
Use active voice. It's clearer and more engaging.
| Passive (avoid) | Active (prefer) |
|---|---|
| "The antenna should be connected to the radio." | "Connect the antenna to the radio." |
| "The frequency was changed by the operator." | "The operator changed the frequency." |
| "It is recommended that you check SWR." | "Check your SWR." |
Second person
Address readers directly as "you" in instructions and guides. It's more engaging than "the user" or "one."
Good: "You'll need a 50-ohm coax cable."
Avoid: "The user will need a 50-ohm coax cable."
Avoid: "One needs a 50-ohm coax cable." Formatting conventions
Lists vs. tables
Choose the right format for your content:
| Format | Use when | Example |
|---|---|---|
| Bulleted list | Items are independent, no particular order matters | Features, requirements, things to bring |
| Numbered list | Sequence matters, steps in a process | Instructions, procedures, rankings |
| Table | Comparing items across multiple attributes | Specifications, before/after, correct/incorrect |
When showing comparisons (correct vs. incorrect, before vs. after), always use a table. It's easier to scan and makes the relationship between items clear.
Headings
Use sentence case for headings—capitalize only the first word and proper nouns.
| Correct | Incorrect |
|---|---|
| Getting started with FT8 | Getting Started With FT8 |
| How to build an antenna | How To Build An Antenna |
| Understanding APRS networks | Understanding APRS Networks |
Numbers
Spell out numbers zero through nine. Use numerals for 10 and above. Always use numerals with units.
| Context | Example |
|---|---|
| Small numbers (0–9) | "Connect three wires" |
| Large numbers (10+) | "Connect 15 wires" |
| With units (always numerals) | "5 watts," "7 MHz," "2 meters" |
| Frequencies | "14.074 MHz" (use decimals) |
| Times | "7:30 PM" (12-hour with AM/PM) |
Abbreviations and acronyms
Spell out terms on first use, followed by the abbreviation in parentheses. Use the abbreviation thereafter.
First use: "The Automatic Packet Reporting System (APRS) enables..."
Subsequent: "APRS stations can be configured to..." Common amateur radio abbreviations (CW, SSB, FM, HF, VHF, UHF) don't need expansion for this audience. Use judgment—if most readers will know it, skip the expansion.
Callsigns
Format callsigns in uppercase: W1ABC, KG7XYZ, JA1ABC. When including a name, use the format "Jane Smith, W1ABC" or "W1ABC (Jane Smith)."
Technical terms
Use code formatting for technical content:
| Type | Example |
|---|---|
| File names | index.md |
| Folder paths | src/content/articles/ |
| Commands | npm run dev |
| Configuration values | true, false |
| Code references | the title field |
Don't use code formatting for general technical terms (antenna, coax, transceiver) or brand names (Yaesu, Icom, Kenwood).
Images
Images add value when they clarify concepts, show equipment, or document activities. Every image should serve a purpose—don't add images just to break up text.
When to use images
| Good uses | Avoid |
|---|---|
| Showing antenna configurations or installations | Generic stock photos of "technology" |
| Documenting club events and activities | Low-quality or blurry photos |
| Illustrating step-by-step procedures | Screenshots that will quickly become outdated |
| Circuit diagrams and schematics | Decorative images with no informational value |
| Equipment photos for reviews or comparisons | Copyrighted images without permission |
Rights and attribution
Only use images you have the right to publish:
- Your own photos — You took it, you can use it
- Club photos — Taken at club events with implied consent
- Creative Commons — Check the specific license (some require attribution, some prohibit commercial use)
- Public domain — No restrictions
- Licensed images — Only if you have explicit permission
Never copy images from Google Image Search, other ham radio sites, or manufacturer websites without explicit permission. "Found it online" is not a license.
When attribution is required, include it in the image caption or immediately below the image:
Photo: John Smith, W1ABC
Image: ARRL, used with permission
Diagram: Creative Commons CC BY-SA 4.0 Aspect ratios
Use consistent aspect ratios for visual harmony:
| Use case | Aspect ratio | Notes |
|---|---|---|
| Article cover images | 16:9 or 3:2 | Landscape orientation works best |
| Event photos | 16:9, 3:2, or 4:3 | Match the natural composition |
| Equipment photos | Match the subject | Don't distort proportions |
| Diagrams and schematics | As needed | Legibility is more important than consistency |
Composition guidelines
- Fill the frame — Get close enough that the subject is clear
- Clean backgrounds — Avoid clutter that distracts from the subject
- Good lighting — Natural light or well-lit environments; avoid harsh shadows
- Horizontal for landscapes — Antenna farms, operating positions, group shots
- Crop thoughtfully — Remove unnecessary elements, but don't cut off important details
People in photos
For club event photos showing identifiable people:
- Attendees at public club events have implied consent for event documentation
- For individual portraits or featured shots, ask permission
- Be mindful of backgrounds (license plates, addresses, computer screens)
- If someone asks to not be photographed or to have a photo removed, honor that request
Alt text
Every image needs descriptive alt text for accessibility. Describe what the image shows, not just what it is.
| Weak alt text | Good alt text |
|---|---|
| "antenna" | "A 20-meter dipole antenna suspended between two trees at approximately 30 feet" |
| "club meeting" | "Fifteen members seated around tables during the January 2026 club meeting" |
| "schematic" | "Circuit schematic showing a simple CW keyer using a 555 timer IC" |
For technical diagrams, the alt text should convey the key information—someone using a screen reader should understand what the diagram illustrates.
Emojis
Emojis are supported in content but should be used sparingly. They can add warmth to social announcements while potentially undermining technical credibility.
When emojis work well
| Context | Example |
|---|---|
| Event announcements | "Join us for Field Day! 📻" |
| Social recaps | "Great turnout at the swapmeet! 🎉" |
| Callout boxes | ⚠️ Warning: High voltage |
| Visual list markers | 📡 Antennas, 🔧 Tools, 📅 Schedule |
When to avoid emojis
| Context | Why |
|---|---|
| Technical documentation | Undermines professional tone |
| Headings | Breaks anchor links, clutters navigation |
| As sole meaning indicator | Not accessible to screen readers |
| Excessive use (more than 2-3 per section) | Becomes distracting, appears unprofessional |
Guidelines
- One or two per section maximum — More becomes noise
- Never in headings — Keep navigation clean
- Pair with text — Don't rely on emoji alone to convey meaning
- Match the tone — Casual for social content, absent for technical
For syntax and how to insert emojis, see the Markdown Reference.
Tags
Tags connect related content across the site. Consistent tagging helps readers discover articles, events, and documentation on topics they care about.
Tag format
| Rule | Correct | Incorrect |
|---|---|---|
| Lowercase | digital-modes | Digital-Modes |
| Hyphens for spaces | field-day | field day |
| Singular form | antenna | antennas |
Exception: Proper nouns keep their capitalization: FT8,
ARRL, POTA.
Guidelines
- Use 2–5 tags — Fewer misses connections; more dilutes the signal
- Be specific —
ft8is better thandigital - Reuse existing tags — Check the tags page before creating new ones
- Tag at multiple levels —
["ft8", "digital-modes", "hf"]
See the Tags Reference for the complete list of current tags and detailed guidance.
Amateur radio conventions
Frequencies
Use MHz for HF and above, kHz for below 1 MHz. Include three decimal places for precision when relevant.
| Band | Format |
|---|---|
| HF | "14.074 MHz" or "7.074 MHz" |
| VHF | "146.52 MHz" or "144.200 MHz" |
| UHF | "446.000 MHz" |
| General reference | "the 20-meter band" or "2 meters" |
Power levels
Use "watts" or "W" with a space: "100 watts" or "100 W." For milliwatts, use "mW."
Q-signals and prosigns
Italicize Q-signals on first use with definitions: QSO (contact), QTH (location), QRM (interference). Common ones like QSO, QSL, and QTH don't need definitions for this audience.
Punctuation
Serial comma
Use the serial comma (Oxford comma) before "and" or "or" in a list of three or more items.
Correct: "You'll need an antenna, coax, and a radio."
Incorrect: "You'll need an antenna, coax and a radio." Dashes
| Type | Use | Example |
|---|---|---|
| Hyphen (-) | Join compound words | "well-known," "20-meter" |
| En dash (–) | Indicate ranges | "pages 10–15," "7–14 MHz" |
| Em dash (—) | Set off phrases for emphasis | "signals—like this—stand out" |
Accessibility
Write content that works for everyone, including people using screen readers or who have visual impairments.
| Element | Guideline | Example |
|---|---|---|
| Image alt text | Describe what the image shows, not just what it is | "Dipole antenna mounted on a portable mast" not "antenna.jpg" |
| Link text | Be descriptive about the destination | "See the setup guide" not "click here" |
| Color | Don't rely on color alone to convey meaning | Use icons or text labels alongside color |
| Headings | Use proper hierarchy, don't skip levels | H1 → H2 → H3, never H1 → H3 |
References
For questions not covered here, consult these resources:
- AP Stylebook — Primary style reference
- Google Developer Documentation Style Guide — Technical writing guidance
- Microsoft Writing Style Guide — Accessible writing
- ARRL Style Guide — Amateur radio terminology