media-publishing-guidelines

name: media-publishing-guidelines description: Comprehensive guidelines for publishing in leading business and technology media outlets (Forbes, TechCrunch, Habr, RBC, etc.), including editorial requirements, pitching strategies, and publication best practices. Use when preparing content for external publication or developing editorial relationships.

Media Publishing Guidelines

When to Use This Skill

Preparing articles for submission to external publications
Pitching article ideas to editors
Understanding editorial requirements of target publications
Building relationships with media outlets
Adapting content for different publication standards
Training writers on publication-specific guidelines

Publication Landscape Overview

Tier 1: Global Business Publications

Forbes, Harvard Business Review, MIT Technology Review

Audience: C-level executives, business leaders, investors Content Focus: Strategic insights, business impact, thought leadership Tone: Professional, authoritative, data-driven Technical Depth: Low (20%) to Medium (40%) Article Length: 800-1,500 words Lead Time: 2-4 weeks

Editorial Priorities:

Business outcomes and ROI
Strategic implications
Executive perspective
Minimal technical jargon
Actionable insights

Pitching Tips:

Lead with business impact, not technology
Include data and research
Demonstrate industry expertise
Connect to current business trends
Offer unique perspective

Tier 2: Technology Publications

TechCrunch, The Verge, Wired, Ars Technica

Audience: Tech professionals, early adopters, innovation enthusiasts Content Focus: Technology trends, product innovation, industry analysis Tone: Conversational, informed, slightly casual Technical Depth: Medium (40%) to High (60%) Article Length: 1,000-2,000 words Lead Time: 1-3 weeks

Editorial Priorities:

News value and timeliness
Innovation and differentiation
Technical credibility
Industry impact
Engaging storytelling

Pitching Tips:

Newsworthiness critical
Technical depth valued
Unique data or insights
Contrarian perspectives welcome
Connect to trending topics

Tier 3: Russian Business Media

Vedomosti (Ведомости), RBC (РБК), Kommersant (Коммерсантъ)

Audience: Russian business leaders, decision-makers, investors Content Focus: Business strategy, market analysis, Russian context Tone: Formal, authoritative, thorough Technical Depth: Low (20%) to Medium (40%) Article Length: 1,000-2,000 words (Russian allows longer) Lead Time: 2-4 weeks

Editorial Priorities:

Russian market relevance
Business impact and economics
Regulatory context (if applicable)
Local examples and case studies
Formal, professional presentation

Pitching Tips:

Emphasize Russian market angle
Include local data and examples
Formal pitch format
Connections and relationships valued
Patience with editorial process

Tier 4: Russian Technology Media

Habr (Хабр), VC.ru, CNews

Audience: Developers, technical professionals, startup community Content Focus: Technical deep-dives, implementation guides, tech trends Tone: Professional but approachable, technical Technical Depth: High (60%) to Very High (80%) Article Length: 1,500-3,000 words (long-form welcome) Lead Time: 1-2 weeks

Editorial Priorities:

Technical accuracy and depth
Practical value
Code examples and details
Honest, not marketing-focused
Community contribution

Pitching Tips:

Technical credibility essential
Practical, implementable content
Code examples required for tutorials
Personal experience valued
Community-first mindset

Publication-Specific Requirements

Forbes

Content Types:

Opinion pieces and commentary
Trend analysis
Leadership insights
Industry predictions

Editorial Guidelines:

Byline must include credentials and expertise
Disclosure of affiliations required
No direct product promotion
Data and sources cited
800-1,200 words optimal

Contributor vs. Staff:

Contributors have more freedom but less distribution
Staff writers have editorial support and homepage placement
Building contributor relationship takes time and quality

Formatting:

Strong headline (8-12 words)
Compelling lede (first 2-3 sentences)
Subheadings for scannability
Bullet lists for key points
2-3 external links to sources
1-2 internal Forbes links (if available)

TechCrunch

Content Types:

News analysis
Product launches and updates
Startup profiles
Trend pieces

Editorial Guidelines:

News angle required (what's new?)
Exclusive data or insights preferred
1,000-1,500 words typical
Conversational but informed tone
Technical accuracy critical

Guest Post Process:

Cold pitches rarely accepted
Warm introductions preferred
Previous publication record helps
Expert credibility required

Formatting:

Strong, newsy headline
Lede with news hook
Supporting details and context
Expert quotes (optional but strong)
Conclusion with implications

Harvard Business Review

Content Types:

Research-backed analysis
Management insights
Strategic frameworks
Case studies

Editorial Guidelines:

Academic rigor expected
Multiple sources required
Data and research essential
1,200-2,000 words
Formal, professional tone

Submission Process:

Highly competitive
Often requires agent or introduction
Multiple rounds of editing
Long lead times (1-3 months)

Formatting:

Strong thesis statement
Literature/research review
Methodology or framework
Business applications
Actionable recommendations

Habr (Хабр)

Content Types / Типы контента:

Technical tutorials / Технические руководства
Architecture deep-dives / Архитектурные разборы
Experience reports / Отчеты об опыте
Technology comparisons / Сравнения технологий

Editorial Guidelines / Редакционные требования:

High technical depth required / Требуется высокая техническая глубина
Code examples mandatory for tutorials / Примеры кода обязательны для руководств
1,500-3,000+ words welcome / 1,500-3,000+ слов приветствуются
Russian language / Русский язык
Markdown formatting / Форматирование Markdown

Community Standards / Стандарты сообщества:

No marketing speak / Без маркетинговой риторики
Honest about limitations / Честность об ограничениях
Practical value essential / Практическая ценность обязательна
Open to discussion and criticism / Открытость к обсуждению и критике

Formatting / Форматирование:

Detailed table of contents / Подробное оглавление
Code blocks with syntax highlighting / Блоки кода с подсветкой синтаксиса
Technical diagrams welcomed / Технические диаграммы приветствуются
References and links to documentation / Ссылки на документацию

VC.ru

Content Types / Типы контента:

Startup stories and lessons / Истории и уроки стартапов
Business model analysis / Анализ бизнес-моделей
Market insights / Рыночные инсайты
Product management / Продуктовый менеджмент

Editorial Guidelines / Редакционные требования:

Business and product focus / Фокус на бизнесе и продукте
Personal experience valued / Личный опыт ценится
1,000-2,000 words typical / 1,000-2,000 слов обычно
Conversational tone acceptable / Разговорный тон приемлем

Community / Сообщество:

Active commenting culture / Активная культура комментирования
Engage with community / Взаимодействие с сообществом
Be prepared to defend ideas / Будьте готовы защищать идеи

Pitching to Editors

The Perfect Pitch Structure

Subject Line / Тема письма:

Clear and specific
Include hook or news angle
Mention credentials if relevant

Examples:

"Pitch: Why 70% of Kubernetes Projects Fail (and How to Fix It)"
"Guest Post Idea: AI Governance Framework for Enterprises"
"Предложение статьи: Как мы снизили затраты на облако на 60%"

Pitch Email Format:

Subject: [Compelling, specific subject line]

Hi [Editor Name],

[Personal connection if any - saw your article on X, we met at Y conference]

I'd like to pitch an article on [TOPIC]:

**Headline**: [Working headline]

**Angle**: [What's new/different/newsworthy about this]

**Why now**: [Timeliness - trend, event, data]

**Why me**: [Your credentials and unique perspective]

**What readers get**: [Key takeaways and value]

**Format**: [Opinion piece, tutorial, analysis] - [estimated word count]

[Optional: Key supporting points]
- Point 1
- Point 2
- Point 3

I can deliver a draft within [timeframe]. Would this be a good fit for [Publication]?

Best regards,
[Name]
[Title, Company]
[Relevant links: LinkedIn, previous articles, etc.]

Pitch Elements to Include

Hook / News Angle:

What makes this timely?
What's the surprising insight?
What data or research backs this?
How does it connect to current trends?

Unique Value:

Why are you the right person to write this?
What unique data or experience do you have?
What perspective can only you provide?

Reader Benefit:

What will readers learn?
What can they do with this information?
How does it help them solve problems?

Evidence of Quality:

Links to previous published articles
Credentials and expertise
Any relevant data or research

Common Pitch Mistakes

❌ Too vague: "I want to write about cloud computing" ✅ Specific: "I want to analyze why 3 of the 5 largest cloud outages in 2024 shared a common architectural flaw—and how enterprises can avoid it"

❌ All about you/company: "Our product is amazing and..." ✅ Reader-focused: "CIOs struggling with [problem] can benefit from [approach] that reduced our costs by 60%"

❌ No research: "I think this would be interesting..." ✅ Data-backed: "According to [source], 67% of companies face [problem]—here's what our research revealed..."

❌ Generic: Could apply to any publication ✅ Targeted: "Given [Publication]'s focus on [topic], this aligns with..."

Editorial Relationships

Building Long-Term Relationships

Start Small:

Comment thoughtfully on articles
Share publication content with insights
Attend publication events/webinars
Build Twitter/LinkedIn connection

Deliver Quality:

First article must be exceptional
Meet deadlines reliably
Respond quickly to editor feedback
Understand publication's audience

Be Professional:

Respect editorial judgment
Don't argue about edits (unless factual errors)
Thank editors publicly
Don't burn bridges

Add Value:

Offer exclusive data or insights
Provide expert sources for other stories
Suggest story ideas (not just your own)
Be reliable expert source

Working with Editors

Understanding the Relationship:

Editors are gatekeepers, not adversaries
Their job: maintain publication quality and serve readers
They know their audience better than you
They've seen thousands of pitches and articles

Responding to Feedback: ✅ Good Response: "Thanks for the feedback. I'll revise the structure and tighten the argument. Will have revised draft by [date]."

❌ Bad Response: "But this is how I want to write it. My way is better."

Handling Rejection:

Thank them for considering
Ask for feedback on why (if they have time)
Ask if a revised angle would work
Try again in 3-6 months with different idea

Deadline Management:

Always meet agreed deadlines
If problem arises, inform immediately (not day-of)
Build buffer into your timeline
Under-promise, over-deliver

Legal and Ethical Considerations

Disclosure Requirements

Must Disclose:

Employment and affiliations
Financial interests in mentioned companies
Paid sponsorships or partnerships
Conflicts of interest

Disclosure Format: "[Author Name] is [Title] at [Company], which provides [brief description]. [Company] competes with [mentioned companies] mentioned in this article."

Copyright and Attribution

When Republishing:

Always get permission from original publication
Use canonical tags to indicate original source
Wait appropriate exclusivity period (typically 30-90 days)
Disclose that article was originally published elsewhere

Citing Others:

Always attribute ideas and quotes
Link to original sources
Paraphrase properly (not just word substitution)
Get permission for extensive quotes

Content Adaptation Strategies

Adapting for Different Publications

Same Core Content, Different Angles:

Original Research: "Analysis of 1,000 Kubernetes Deployments"

For HBR: "What Enterprise Kubernetes Deployments Reveal About Digital Transformation ROI"

Focus: Business outcomes and strategic insights
Audience: C-level
Length: 1,500 words
Data: Cost savings, time-to-market improvements

For TechCrunch: "Kubernetes Adoption Study: 73% of Teams Underestimate Complexity"

Focus: Industry trend and practical challenges
Audience: Tech professionals
Length: 1,200 words
Data: Adoption challenges, tooling gaps

For Habr: "Детальный анализ 1000 Kubernetes-кластеров: архитектурные паттерны и антипаттерны"

Focus: Technical deep-dive and implementation patterns
Audience: Developers and architects
Length: 2,500 words
Data: Configuration patterns, performance metrics

Repurposing Content Effectively

One Research Study → Multiple Articles:

Executive Summary: Brief analysis for LinkedIn (500 words)
Trend Analysis: Business implications for Forbes (1,000 words)
Technical Deep-Dive: Implementation guide for Habr (2,500 words)
Case Study: Specific customer story for company blog (1,500 words)
Whitepaper: Comprehensive report with methodology (5,000+ words)

Best Practices:

Adapt angle and depth, not just length
Respect exclusivity periods
Each version should feel native to platform
Don't just republish verbatim

Measurement and Success Metrics

Article Performance Metrics

Reach:

Page views / unique visitors
Social shares and engagement
Time on page
Newsletter inclusion
Homepage feature

Engagement:

Comments and discussion quality
Social media conversation
Inbound links and citations
Email responses and inquiries

Business Impact:

Lead attribution
Brand awareness lift
Speaking invitations
Partnership inquiries
Sales opportunities

Building Publication Track Record

Quality Over Quantity:

One Forbes article > Ten unknown blog posts
Tier 1 publications build credibility
Consistent quality > volume

Portfolio Development:

Save links to all published articles
Screenshot social engagement
Collect reader testimonials
Track business outcomes
Update media kit quarterly

Checklist for Publication Submission

Pre-Submission Checklist

Research publication: Read recent articles, understand audience and style
Review guidelines: Follow publication-specific requirements
Verify facts: All claims checked and sourced
Test code: All code examples run correctly
Check length: Within target word count range
Optimize headline: Clear, compelling, appropriate
Write meta description: 150-160 characters
Include bio: Credentials and expertise clear
Add disclosures: Conflicts of interest disclosed
Proofread: Grammar, spelling, formatting perfect
Get internal review: Stakeholder approval if needed
Prepare images: High-quality, properly sized, rights cleared

Post-Publication Actions

Thank editor: Acknowledge editor's work publicly
Share widely: Distribute on social media and newsletters
Engage with comments: Respond to reader questions
Monitor metrics: Track performance
Follow up with leads: Respond to inquiries
Update portfolio: Add to published work list
Analyze performance: Learn what resonated
Plan next pitch: Build on success

References

references/publication-directory.md - Detailed directory of publications with contacts
references/pitch-templates.md - Pitch email templates for different scenarios
assets/successful-pitches.md - Real examples of successful pitches

Related Skills

enterprise-storytelling - Crafting narratives for different publications
editorial-excellence - Meeting publication quality standards