Style Guide

This guide keeps our stories consistent and easy to read. We follow AP style for anything not covered here. Where this guide and AP disagree, this guide wins. For how we report and verify, see our editorial standards.

Voice and tone

• Write for a smart reader who plays Roblox but may not follow developer news. Explain jargon once.
• Be clear, direct and calm. Let the facts carry the weight instead of adjectives.
• Avoid hype words such as insane, massive, huge, shocking and game-changing. Say what happened and why it matters.
• Use active voice. “Roblox removed the game,” not “The game was removed.”
• Keep paragraphs short: one idea each, usually one to three sentences.

Headlines

• Use title case, and keep headlines under about 70 characters so they aren’t cut off in search.
• Lead with the news: who did what. Put the most important word near the start.
• The headline must be supported by the story. No bait, and no question headlines the story can’t answer.
• Mark unconfirmed news in the headline itself, for example with “reportedly” or “leak.”
• Use numerals in headlines, including for numbers under 10.

Ledes and structure

The first paragraph tells the reader what happened, who it affects and why it matters now. Context and background come after. Put a short “why it matters” or “what’s next” near the end of longer stories. Use subheadings to break up anything longer than about 600 words.

Attribution and quotes

• Use “said” for spoken or written quotes. Avoid “claimed,” “admitted” and “slammed,” which suggest judgment.
• Attribute every fact that isn’t common knowledge: “according to the DevForum post.”
• Link to the original source the first time you cite it.
• Don’t change quotes except to fix obvious typos in written statements. Use [brackets] for clarifying words and an ellipsis (…) for cuts.
• Quote social media posts accurately, including the account’s @handle.

Names, usernames and games

• Developers and creators: use the name they publicly go by. On first mention, include their username if it differs, e.g. “Jordan (@BuilderJordan).” Use only the public name after that.
• Game titles are written exactly as their creators style them, without italics or quotes.
• Groups and studios are written as they appear on Roblox.
• Don’t name minors or private individuals. See our standards on protecting young people.

Roblox terminology

Numbers, money and dates

• Spell out one through nine. Use numerals for 10 and up, and for all ages, percentages and currency.
• Write large figures as numerals plus a word: 2.4 million visits, 150,000 players. Avoid “2.4M” in body copy.
• When converting Robux to real money, say which rate you used (for example, the DevEx rate) and give the currency: about $3.50 USD.
• Dates: Oct. 24, 2026. Avoid “yesterday” and “last week,” which go stale. Include a time zone with times: 2 p.m. ET.

Punctuation and spelling

• American English spelling.
• No Oxford comma unless it’s needed to avoid confusion.
• One space after a period. Use em dashes sparingly.
• Avoid exclamation marks outside of quotes and game titles.
• Spell out abbreviations on first mention unless readers universally know them, like FPS or PC.

Links, images and accessibility

• Link descriptive words, not “click here.”
• Every image needs alt text that describes what it shows, and a credit when it isn’t ours.
• Don’t put important information only in an image. Repeat it in the text.
• Never link to exploits, scams, stolen assets or sites that ask for Roblox logins.

Live updates

• Lead each update with the newest fact in one or two sentences.
• Every update is timestamped. Don’t edit earlier updates except to correct them, and say when you do.
• When the event ends, post a short summary at the top of the live page.

Tags and labels

Each story gets one primary topic tag, which appears above the headline. Use Opinion for opinion pieces, Analysis for analysis, and Sponsored for any paid placement. Breaking stories use the live label only while they are actively being updated.

Corrections

Correction notes go at the end of the story, in italics, and state the fix plainly: “Correction, Oct. 24, 2026: An earlier version of this story misstated the date of RDC.” Don’t repeat the error in full.

Last updated: October 24, 2026