Community guidelines

[KyleMit]

Introduces a new 'Community' section to Stacks to initially help writing on Meta.

• Audiences: Breaks down the types of users, their expectations and how to write to them.
• Tone: How our main ToV should differ for users.
• Language & Grammar: Again, a derivative of the main guidance.
• Terminology: Glossary of terms for Public Platforms specifically.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3e95f20

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for stacks ready!

Name	Link
🔨 Latest commit	3e95f20
🔍 Latest deploy log	https://app.netlify.com/projects/stacks/deploys/6a690da4b9f0600008ba740c
😎 Deploy Preview	https://deploy-preview-2299--stacks.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[abovedave]

@someobscurereference incorporated your #2309 PR (here), alt text and the extra bits.

[dancormier]

Looking good 😎 I added commits with very minor conditional hardening, plus a couple language tweaks for more inclusive accessibility wording and clarity around meta site purpose/structure. Feel free to alter my changes as you see fit and merge when ready!

[netlify]

✅ Deploy Preview for stackoverflow-email ready!

Name	Link
🔨 Latest commit	3e95f20
🔍 Latest deploy log	https://app.netlify.com/projects/stackoverflow-email/deploys/6a690da4c825540009c60813
😎 Deploy Preview	https://deploy-preview-2299--stackoverflow-email.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[CGuindon]

Chiming in on the information architecture here, my suggestion:

• Community currently sits as its own top-level section, parallel to Copywriting. Both are about how we write (product copy vs. writing to the community on Meta), so let's group them:

Words
├── Copywriting (Tone of voice, Naming, Style guide, Patterns)
└── Community (Audiences, Tone, Language & grammar, Terminology)

CURRENT

PROPOSED

---

Notes on rationale and thinking — if you or my future self wants context

Summary

Community currently sits as its own top-level nav item, parallel to Copywriting. Both sections are fundamentally about how we write — Copywriting covers product/marketing copy (Tone of voice, Naming, Style guide, Patterns), Community covers writing to people on Meta (Audiences, Tone, Language & grammar, Terminology) — but nothing in the IA currently reflects that relationship.

Problem

• Two disconnected top-level sections for closely related content makes the writing guidance harder to discover as a set.
• Community and Copywriting have overlapping sub-topic names (e.g. "Tone" vs. "Tone of voice") with different rules, which could get confusing without a name change or repositioning.

Proposed change

Introduce a new top-level parent, Words, with Copywriting and Community as sibling sections underneath:

Words
├── Copywriting
│   ├── Tone of voice
│   ├── Naming
│   ├── Style guide
│   └── Patterns
└── Community
    ├── Audiences
    ├── Tone
    ├── Language & grammar
    └── Terminology

Why a shared parent rather than nesting Community under Copywriting directly

• Avoids the naming collision between "Tone of voice" and "Tone."
• Keeps both sections equally visible in nav, rather than implying Community is a subset of product copy.
• Leaves room for Community to grow beyond pure writing guidance (e.g. moderation tone, escalation) without outgrowing a "Copywriting" label.

Alternatives considered

1. Nest Community under Copywriting as-is (requires renaming sub-items to avoid clashes).
2. Leave Community as a separate top-level section (status quo — no discoverability link between the two).

Name options considered for new parent

• Words (chosen: simple, friendly, very on-brand for a design system that likes plain language; slightly casual but could work well ("Words" as a nav item is punchy))
• Voice (second choice)
• Content
• Writing
• Voice & Writing (like it but wanted to keep it 1 word like all other items)

[dancormier]

@CGuindon I agree the IA could use some adjustment. I'd consider it out of scope for this PR but I've created STACKS-912 so we don't lose track of this work