mirror of
https://github.com/pacnpal/thrillwiki_django_no_react.git
synced 2025-12-20 12:11:13 -05:00
feat: complete monorepo structure with frontend and shared resources
- Add complete backend/ directory with full Django application - Add frontend/ directory with Vite + TypeScript setup ready for Next.js - Add comprehensive shared/ directory with: - Complete documentation and memory-bank archives - Media files and avatars (letters, park/ride images) - Deployment scripts and automation tools - Shared types and utilities - Add architecture/ directory with migration guides - Configure pnpm workspace for monorepo development - Update .gitignore to exclude .django_tailwind_cli/ build artifacts - Preserve all historical documentation in shared/docs/memory-bank/ - Set up proper structure for full-stack development with shared resources
This commit is contained in:
pacnpal
290
shared/docs/moderation_guide.md
Normal file
290
shared/docs/moderation_guide.md
Normal file
@@ -0,0 +1,290 @@
|
||||
# ThrillWiki Moderation Guide
|
||||
|
||||
## Overview
|
||||
|
||||
This guide covers the moderation systems in ThrillWiki, including:
|
||||
- Content edit submissions
|
||||
- Photo submissions
|
||||
- User reviews
|
||||
- Report handling
|
||||
- Moderation best practices
|
||||
|
||||
## Moderation Dashboard
|
||||
|
||||
Access the moderation dashboard at `/moderation/` to view:
|
||||
- Pending edit submissions
|
||||
- Photo submissions awaiting review
|
||||
- Reported content
|
||||
- Moderation statistics
|
||||
|
||||
## Content Edit Moderation
|
||||
|
||||
### Edit Submission Types
|
||||
1. **Edit Existing**
|
||||
- Changes to existing parks, rides, or other content
|
||||
- Shows diff of proposed changes
|
||||
- Requires source verification
|
||||
|
||||
2. **Create New**
|
||||
- New park, ride, or content submissions
|
||||
- Requires complete information
|
||||
- Needs source verification
|
||||
|
||||
### Review Process
|
||||
1. **Initial Assessment**
|
||||
- Check submission completeness
|
||||
- Verify sources
|
||||
- Review user history
|
||||
|
||||
2. **Status Options**
|
||||
```python
|
||||
STATUS_CHOICES = [
|
||||
('NEW', 'New'),
|
||||
('APPROVED', 'Approved'),
|
||||
('REJECTED', 'Rejected'),
|
||||
('ESCALATED', 'Escalated'),
|
||||
]
|
||||
```
|
||||
|
||||
3. **Actions**
|
||||
- Approve: Apply changes after verification
|
||||
- Reject: Provide clear reason
|
||||
- Escalate: For complex cases needing admin review
|
||||
|
||||
### Approval Guidelines
|
||||
- Verify information accuracy
|
||||
- Check reliable sources
|
||||
- Ensure formatting consistency
|
||||
- Review for completeness
|
||||
|
||||
### Rejection Guidelines
|
||||
- Provide clear explanation
|
||||
- Reference guidelines
|
||||
- Suggest improvements
|
||||
- Be constructive
|
||||
|
||||
## Photo Moderation
|
||||
|
||||
### Submission Types
|
||||
- Park photos
|
||||
- Ride photos
|
||||
- Attraction photos
|
||||
- Historical photos
|
||||
|
||||
### Review Process
|
||||
1. **Initial Check**
|
||||
- Image quality
|
||||
- Appropriate content
|
||||
- Copyright concerns
|
||||
- Metadata accuracy
|
||||
|
||||
2. **Status Options**
|
||||
```python
|
||||
STATUS_CHOICES = [
|
||||
('NEW', 'New'),
|
||||
('APPROVED', 'Approved'),
|
||||
('REJECTED', 'Rejected'),
|
||||
('AUTO_APPROVED', 'Auto Approved'),
|
||||
]
|
||||
```
|
||||
|
||||
3. **Actions**
|
||||
- Approve: Add to main gallery
|
||||
- Reject: Explain issues
|
||||
- Auto-approve: For trusted users
|
||||
|
||||
### Photo Guidelines
|
||||
- Minimum resolution requirements
|
||||
- No watermarks
|
||||
- Clear and focused
|
||||
- Appropriate content
|
||||
- Proper attribution
|
||||
|
||||
## Review Moderation
|
||||
|
||||
### Review Components
|
||||
- Rating (1-10)
|
||||
- Written content
|
||||
- Visit date
|
||||
- Optional photos
|
||||
|
||||
### Moderation Criteria
|
||||
1. **Content Standards**
|
||||
- Constructive feedback
|
||||
- No personal attacks
|
||||
- Family-friendly language
|
||||
- Factual accuracy
|
||||
|
||||
2. **Rating Consistency**
|
||||
- Check against written content
|
||||
- Compare with average ratings
|
||||
- Look for rating abuse
|
||||
|
||||
3. **Photo Guidelines**
|
||||
- Relevant to review
|
||||
- Appropriate content
|
||||
- Quality standards
|
||||
|
||||
### Report Handling
|
||||
1. **Review Reports**
|
||||
- Assess reported content
|
||||
- Check reporter history
|
||||
- Verify claims
|
||||
|
||||
2. **Actions**
|
||||
- Remove inappropriate content
|
||||
- Edit/update if needed
|
||||
- Notify users
|
||||
- Document actions
|
||||
|
||||
## Best Practices
|
||||
|
||||
### General Guidelines
|
||||
1. **Consistency**
|
||||
- Follow established guidelines
|
||||
- Apply rules uniformly
|
||||
- Document decisions
|
||||
|
||||
2. **Communication**
|
||||
- Clear explanations
|
||||
- Professional tone
|
||||
- Constructive feedback
|
||||
|
||||
3. **Escalation**
|
||||
- Know when to escalate
|
||||
- Document complex cases
|
||||
- Seek admin input
|
||||
|
||||
### Quality Control
|
||||
1. **Content Standards**
|
||||
- Accuracy
|
||||
- Completeness
|
||||
- Formatting
|
||||
- Source verification
|
||||
|
||||
2. **User Management**
|
||||
- Track user history
|
||||
- Identify trusted contributors
|
||||
- Handle problem users
|
||||
|
||||
3. **Documentation**
|
||||
- Record decisions
|
||||
- Note special cases
|
||||
- Track patterns
|
||||
|
||||
## Moderation Tools
|
||||
|
||||
### Edit Submission Tools
|
||||
```python
|
||||
def approve(self, user):
|
||||
"""Approve and apply changes"""
|
||||
# Validates and applies changes
|
||||
# Updates status
|
||||
# Records moderator action
|
||||
|
||||
def reject(self, user):
|
||||
"""Reject submission"""
|
||||
# Updates status
|
||||
# Records moderator action
|
||||
# Notifies user
|
||||
|
||||
def escalate(self, user):
|
||||
"""Escalate to admin"""
|
||||
# Marks for admin review
|
||||
# Records moderator action
|
||||
```
|
||||
|
||||
### Photo Submission Tools
|
||||
```python
|
||||
def approve(self, moderator, notes=''):
|
||||
"""Approve photo"""
|
||||
# Moves to main gallery
|
||||
# Updates status
|
||||
# Records approval
|
||||
|
||||
def reject(self, moderator, notes):
|
||||
"""Reject photo"""
|
||||
# Updates status
|
||||
# Records rejection reason
|
||||
# Notifies user
|
||||
```
|
||||
|
||||
## Special Cases
|
||||
|
||||
### Content Disputes
|
||||
1. **Handling Conflicts**
|
||||
- Review all perspectives
|
||||
- Check reliable sources
|
||||
- Document decisions
|
||||
- Consider escalation
|
||||
|
||||
2. **Resolution Process**
|
||||
- Gather evidence
|
||||
- Consult experts if needed
|
||||
- Make documented decision
|
||||
- Communicate clearly
|
||||
|
||||
### Emergency Situations
|
||||
1. **Immediate Action Needed**
|
||||
- Inappropriate content
|
||||
- Copyright violations
|
||||
- Personal information
|
||||
- Harmful content
|
||||
|
||||
2. **Response Protocol**
|
||||
- Remove content immediately
|
||||
- Document action taken
|
||||
- Notify administrators
|
||||
- Follow up as needed
|
||||
|
||||
## Moderation Workflow
|
||||
|
||||
1. **Daily Tasks**
|
||||
- Review new submissions
|
||||
- Check reported content
|
||||
- Handle escalations
|
||||
- Update documentation
|
||||
|
||||
2. **Weekly Tasks**
|
||||
- Review moderation patterns
|
||||
- Check for recurring issues
|
||||
- Update guidelines if needed
|
||||
- Team communication
|
||||
|
||||
3. **Monthly Tasks**
|
||||
- Review statistics
|
||||
- Assess guidelines
|
||||
- Plan improvements
|
||||
- Team training
|
||||
|
||||
## Resources
|
||||
|
||||
### Reference Materials
|
||||
- Content guidelines
|
||||
- Photo standards
|
||||
- Review policies
|
||||
- Escalation procedures
|
||||
|
||||
### Support Channels
|
||||
- Admin contact information
|
||||
- Team communication
|
||||
- Emergency procedures
|
||||
- Legal resources
|
||||
|
||||
## Training and Development
|
||||
|
||||
1. **New Moderator Training**
|
||||
- Platform overview
|
||||
- Tools introduction
|
||||
- Guidelines review
|
||||
- Supervised practice
|
||||
|
||||
2. **Ongoing Development**
|
||||
- Regular updates
|
||||
- Case studies
|
||||
- Best practices
|
||||
- Team feedback
|
||||
|
||||
## Conclusion
|
||||
|
||||
Effective moderation is crucial for maintaining ThrillWiki's quality and community. Follow these guidelines consistently while using good judgment for special cases. Document decisions and seek help when needed.
|
||||
Reference in New Issue
Block a user