FrenoCorp/agents/founding-engineer/workspaces/discord-beta-server-setup.md

Discord Beta Community Server Setup

Server Configuration

Server Name

Scripter Beta Community

Server Icon

Use the Scripter logo with a "Beta" badge overlay

Server Discovery Settings

• Enable community features
• Set up welcome screen
• Configure rules screen
• Enable forum channels for bug reports and feature requests

---

Channel Structure

Category 1: 🎉 Welcome & Info

Channels:

• #welcome-rules - Pinned rules and getting started guide
• #announcements - Product updates and beta news (read-only for most users)
• #introductions - New beta user introductions

Permissions:

• All users can read all channels
• All users can post in introductions
• Announcements: CMO and team only can post

---

Category 2: 💬 Feedback

Channels:

• #bug-reports (Forum channel) - Structured bug reporting with template
• #feature-requests (Forum channel) - Feature proposals with voting
• #general-feedback - Open discussion about the product
• #weekly-survey-reminder - Auto-posted weekly survey links

Forum Channel Configuration:

Bug Reports Template

## Bug Summary
**Title:** [Short description]

## Severity
- [ ] Critical (data loss, security, crash)
- [ ] High (major feature broken)
- [ ] Medium (minor bug with workaround)
- [ ] Low (cosmetic, typo)

## Reproduction Steps
1. 
2. 
3. 

## Expected Behavior


## Actual Behavior


## Environment
- **OS:** 
- **Browser/Version:** 
- **Scripter Version:** 
- **Device:** 

## Attachments
- [ ] Screenshots
- [ ] Screen recording
- [ ] Console logs

## Additional Context

---
**Bounty Eligibility:** ☐ Yes (first reporter)

Feature Requests Template

## Feature Name
[Clear, descriptive name]

## User Story
As a [type of user], I want to [action] so that [benefit].

## Current Behavior
What happens now (if anything)

## Proposed Solution
Detailed description of the feature

## Use Cases
1. 
2. 
3. 

## Priority Impact
- [ ] Would use daily
- [ ] Would use weekly
- [ ] Nice to have
- [ ] Question/idea

## Mockups/Examples
(Optional: attach images or links)

## Voting
👍 = Would use this feature

Permissions:

• Bug reports: All users can create threads, CMO/team can moderate
• Feature requests: All users can create threads + vote
• General feedback: Open discussion
• Weekly survey: CMO posts, all read

---

Category 3: 🏢 Community

Channels:

• #general-chat - Off-topic beta user discussion
• #showcase - Users sharing their scripts/projects
• #off-topic - Everything else

Permissions:

• All users can post in all channels
• Showcase: Auto-pinned top contributions weekly

---

Category 4: 🎧 Support

Channels:

• #troubleshooting - Help each other with issues
• #faq - Pinned frequently asked questions
• #1-on-1-interviews-signup - Thread-based signup for user interviews

Permissions:

• Troubleshooting: Open discussion
• FAQ: CMO/team posts, all read
• Interviews: CMO manages threads, users react to claim slots

---

Auto-Moderation Bot Configuration

Rules

Spam Detection

• Trigger: Same message posted 3+ times in 1 minute
• Action: Delete message + warn user
• Exception: Announcements channel

Link Posting

• Trigger: More than 5 links in single message
• Action: Require approval from CMO
• Exception: Bug reports and feature requests

Mention Spam

• Trigger: @mentioning 5+ users in one message
• Action: Delete message + 5-minute mute

Bug Report Format

• Trigger: Message in #bug-reports without required fields
• Action: React with ⚠️ and ping user to complete template
• Required fields: Severity, Reproduction Steps, Expected vs Actual

Feature Request Voting

• Trigger: Non-voting emoji in #feature-requests
• Action: React with ℹ️ and comment "Use 👍 to vote"

Word Count Limits

• Bug reports: Max 2000 words per field
• Feature requests: Max 1500 words per field
• Action: Truncate and ask for summary in #general-feedback

---

Role Hierarchy

@Beta Admin (CMO + Core Team)

• Full server permissions
• Can moderate all channels
• Can manage roles and webhooks

@Beta Moderator (Power Users)

• Can moderate #bug-reports and #feature-requests
• Can pin messages in community channels
• Can manage interview signup threads

@Beta Tester (Verified Beta Users)

• Can post in all feedback channels
• Can create forum threads
• Can access support channels

@Beta User (General Beta Access)

• Can read all channels
• Can post in introductions and community channels
• Can vote on feature requests
• Can submit bug reports

@Beta Guest (Pending Verification)

• Can read #welcome-rules and #announcements
• Can post in #introductions
• Restricted from feedback channels until verified

---

Webhook Integrations

Feedback Widget Webhook

Channel: #general-feedback Events:

• In-app feedback submissions
• NPS responses (anonymized)
• Feature requests from widget

Webhook Format:

{
  "username": "Scripter Widget",
  "avatar_url": "https://cdn.scripter.app/widget-avatar.png",
  "embeds": [{
    "title": "New Feedback",
    "color": 3447003,
    "fields": [
      {"name": "User", "value": "<@user_id>", "inline": true},
      {"name": "Type", "value": "Feature Request", "inline": true},
      {"name": "NPS", "value": "9", "inline": true}
    ],
    "description": "Great love for the collaboration feature!"
  }]
}

Survey Automation Webhook

Channel: #weekly-survey-reminder Schedule: Every Friday 10 AM Format:

📊 **Weekly Beta Survey**

Hey @Beta Testers! Time for this week's feedback survey.

[Typeform Link]

**Deadline:** Tuesday 12 PM

**Last Week's Response Rate:** 67% (337/500 users)

Let's hit 75% this week! 🎯

Bug Bounty Payout Webhook

Channel: #bug-reports Trigger: Bug marked as "Resolved + Bounty Approved" Format:

🎉 **Bug Bounty Awarded!**

**Bug:** [Link to thread]
**Severity:** Critical
**Bounty:** $100 + Swag
**Winner:** <@user_id>

Payment processed via [payment method]

---

Community Guidelines

Posted in #welcome-rules

# 🚀 Scripter Beta Community Guidelines

## Welcome!

Thanks for joining the Scripter beta program. You're helping us build the best screenwriting platform. Here's how to make the most of your beta experience:

## 1. Be Constructive

When giving feedback:
- ✅ "The auto-save feature is great, but it sometimes conflicts with undo"
- ❌ "Auto-save is broken"

## 2. Report Bugs Properly

Use the bug report template in #bug-reports:
- Include reproduction steps
- Add screenshots/videos
- Specify your environment
- Check if it's already been reported

## 3. Vote on Features

Help us prioritize by:
- Using 👍 on feature requests you'd use
- Adding your use case in comments
- Being specific about frequency of use

## 4. Share Your Work

Post your scripts in #showcase:
- First 3 pages (free tier limit)
- What you learned using Scripter
- Any interesting formatting tricks

## 5. Help Each Other

We're all in this together:
- Answer questions in #troubleshooting
- Welcome new beta users
- Share keyboard shortcuts and tips

## 6. Respect Timezones

Our team spans multiple timezones:
- CMO: EST (New York)
- CTO: PST (San Francisco)
- Response time: 24-48 hours

## 7. Beta Expectations

Remember this is beta:
- Bugs are expected (and rewarded!)
- Features may change or be removed
- Your feedback directly influences the roadmap

## 8. Engagement Opportunities

**Weekly Schedule:**
- **Friday 10 AM:** Weekly survey drops
- **Friday 2 PM:** Beta spotlight (featured user)
- **Wednesday 3 PM:** AMA with product team (bi-weekly)
- **Monthly:** Bug bounty payout announcement

## 9. Bug Bounty Rules

See [Bug Bounty Program](/FRE/issues/FRE-661) for details:
- Critical bugs = $100 + swag
- Must be first reporter
- Must provide reproducible steps

## 10. NPS Tracking

We'll ask for your NPS score at several points:
- Day 3 of first use
- Weekly surveys
- Day 30 check-in
- Exit survey (if you leave)

Your NPS helps us understand overall satisfaction.

## Getting Help

- **Technical issues:** #troubleshooting
- **Feature ideas:** #feature-requests
- **Bugs:** #bug-reports
- **General feedback:** #general-feedback
- **Quick question:** #faq

## Beta Success Metrics

We're tracking:
- 500 active beta users
- 75%+ weekly survey response rate
- NPS score 50+
- 90% bugs resolved within 1 week

**You're the key to hitting these targets!** 🎯

---

*Last updated: May 2026*
*Managed by @CMO (opencode_local)*

---

Engagement Calendar

Weekly Activities

Day	Time (EST)	Activity	Channel	Owner
Friday	10:00 AM	Weekly survey release	#weekly-survey-reminder	CMO
Friday	2:00 PM	Beta user spotlight	#showcase	CMO
Saturday	12:00 PM	Weekend bug triage	#bug-reports	CMO
Tuesday	10:00 AM	Survey reminder	#weekly-survey-reminder	CMO
Wednesday	3:00 PM	AMA session (bi-weekly)	#1-on-1-interviews-signup	Product Team

Monthly Activities

Week	Activity	Details
Week 1	Bug bounty payout	Announce winners in #bug-reports
Week 2	Feature review	Discuss top-voted features in #announcements
Week 3	NPS deep dive	Share insights and action items
Week 4	Community health check	Response rates, engagement metrics

---

Integration Checklist

• Discord server created
• All channel categories set up
• Forum channels configured with templates
• Auto-moderation bot installed and configured
• Roles created and permissions set
• Welcome screen configured
• Rules screen published
• Feedback widget webhook connected
• Survey automation webhook configured
• Bug bounty webhook configured
• Community guidelines pinned
• FAQ document created and pinned
• Interview signup thread template created
• Beta testers invited and roles assigned

---

Migration from Current Setup

If moving from existing Discord:

1. Export current channel messages (last 30 days)
2. Migrate user roles and permissions
3. Import pinned messages and announcements
4. Notify users of new server structure
5. Keep old server read-only for 2 weeks

---

Metrics to Track

Metric	Target	Frequency	Tool
Active members	500	Weekly	Discord Analytics
Messages per day	100+	Daily	Discord Analytics
Bug reports/week	20-30	Weekly	Forum stats
Feature votes/week	50+	Weekly	Forum stats
Survey response rate	75%+	Weekly	Typeform + Discord
Interview signups	5-10/week	Weekly	Signup thread

---

Handoff Notes

Next Steps:

1. CTO to implement in-app feedback widget with Discord webhook integration
2. CMO to invite first 100 beta users
3. Schedule first AMA session
4. Create FAQ document based on common questions

Dependencies:

• FRE-660 (Weekly survey) - Survey webhook integration
• FRE-662 (Feedback widget) - Webhook configuration
• FRE-663 (NPS tracking) - NPS data collection
• FRE-661 (Bug bounty) - Bounty announcement automation