Discussions Guide

Learn how to use discussions for in-content comments and team collaboration.

Overview

Discussions allow teams to:

Comment on specific content fields
Ask questions about content
Request changes
Track feedback history

Starting Discussions

Comment on Specific Field

Start discussion on headline field for story 123:
"Should this headline be more specific about the product name?"

Request Changes

Create discussion on hero image:
"Can we get a higher resolution version of this image?
Current size is too small for desktop displays."

Ask Questions

Comment on product description:
"Is this pricing information still current?
I thought we updated prices last month."

Managing Discussions

Viewing Discussions

Show me all discussions for story "Product Launch"

Show all unsolved discussions across all blog posts

Replying to Discussions

Reply to discussion 456:
"I've updated the image to a higher resolution version.
Please review and let me know if it works better."

Resolving Discussions

Mark discussion 789 as resolved after fixing the issue

Discussion Workflows

Content Review Process

1. Author creates content
2. Reviewer starts discussions on fields needing work
3. Author addresses each discussion
4. Author replies when fixed
5. Reviewer verifies and resolves discussions
6. Once all resolved, content approved

Collaborative Editing

1. Multiple editors review same content
2. Each starts discussions on their areas
3. Content owner triages feedback
4. Addresses highest priority items first
5. Closes discussions as completed

Best Practices

Be specific - Comment on exact fields, not whole stories
@mention - Tag relevant team members
Clear actions - State what needs to be done
Resolve promptly - Close discussions when addressed
Use for questions - Don't communicate via discussions for general chat

Common Scenarios

Editorial Feedback

Editor starts discussions:
- Headline: "Consider making this more SEO-friendly"
- Intro: "This paragraph is too long, can we split it?"
- Body: "Add link to related product page here"

Image Review

Designer comments on images:
- Hero image: "Needs better crop for mobile"
- Product shot: "Background should be white, not gray"
- Team photo: "Update with current headshots"

Legal Review

Legal team flags concerns:
- Pricing: "Add disclaimer about regional variations"
- Claims: "Need source for this statistic"
- Terms: "Link to updated terms of service"

Need help with discussions? Ask Claude to show you discussions that need attention!