Editorial Guidelines Strategy

Objectives

Create a consistent, scalable editorial system that maintains authenticity, quality, and hyperlocal relevance across all user-generated and in-house content

Structure

Editorial Mission Statement:

“Amplify Black community voices with hyperlocal, culturally relevant storytelling that informs, connects, and empowers.”

Content Pillars:

• • Local Events & News: Neighborhood news, civic updates, community events.
  • Personal Stories: Lived experiences, personal essays, community reflections.
  • Resource Spotlights: Features on local businesses, services, programs.
  • Culture & Creativity: Arts, music, food, traditions, and emerging talent.
  • Advocacy & Awareness: Civic issues, social justice topics, calls to action.

Submission Types:

• • Articles (300–800 words)
  • Short posts (under 300 words)
  • Photo Essays
  • Event Listings
  • Community Announcements

Editorial Standards:

• • Authenticity First: Real voices over “professional polish.” Natural, conversational, passionate writing is encouraged.
  • Fact-Checking: Verify dates, names, and key facts—especially for local news.
  • Community Respect: Content must uphold dignity, avoid stereotyping, and reinforce community pride.
  • Language Sensitivity: Avoid oppressive or exclusionary language. Promote inclusive storytelling.
  • Source Attribution: Credit local organizations, media, or individuals when referencing external work.

Editorial Review Process:

• Light editorial touch focused on clarity, grammar, and alignment with values — not heavy rewriting.
• Contributors retain their voice unless they violate community or editorial guidelines.

Tone of Voice Documentation

Objective:

Establish a recognizable, trustworthy brand voice that embodies HfYC’s core values — warmth, empowerment, authenticity, and community pride.

Tone Attributes:

Voice vs. Style:

• Voice remains consistent (warm, empowering).
• Style flexes slightly depending on format (articles = slightly more structured; social posts = looser, punchier).

Language Guide:

• Prefer plain, powerful English over corporate jargon.
• Encourage first-person stories (“I experienced…” or “We did…”).
• Promote use of local expressions and cultural references where appropriate.
• Emphasize short, direct sentences for digital readability.
• Pronouns: Use “we,” “you,” “our community” — inclusive language.

Types of Content We Publish:

Content Submission Templates

Objective:

Lower the barriers for contributors by offering clear, easy-to-follow content templates that guide quality submissions.

Article Submission Template

Title:
(Short, punchy, informative)

Author Name:
(You can use a nickname or full name)

City/Neighborhood:
(E.g., “Newark Central,” “East Atlanta”)

Article Type:
(Story, News, Event, Resource Spotlight, Opinion)

Main Body:
(Aim for 300–800 words)

Key Points to Cover (Optional prompts):

• What’s the story/event/resource?
• Why does it matter to the community?
• How can people get involved or benefit?

Photos:
(Attach 1–3 photos, if available — must be original or have permission)

Short Post Template

Title:
(Optional for shorter posts)

Content:
(100–300 words; direct, heartfelt, or informative)

Tag:
(Choose one: Event | News | Story | Resource | Shoutout)

Photo Essay Template

Title:
(Capture the spirit of the photo story)

Photographer Name:

City/Neighborhood:

Photo Captions:

• 3–8 photos with 1–2 sentence captions explaining the moment or story.

Event Submission Template

Event Name:

Organizer:

Date and Time:

Location:

Description:
(50–150 words about what it is and who should attend)

How to Join:
(Link or instructions)

Optional: Upload Flyer or Image

Content Submission Guidelines (Quick Check)

✅ Respect privacy: Get permission if sharing images/stories about others.
✅ Stay factual: Double-check facts before submitting.
✅ Be community-centered: Focus on topics that uplift or inform.
✅ No hate speech, discrimination, or promotion of harmful content.
✅ HfYC reserves the right to edit for clarity, length, and community standards.