mirror of
https://github.com/pacnpal/thrillwiki_django_no_react.git
synced 2025-12-20 08:31:08 -05:00
- 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
5.9 KiB
5.9 KiB
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
-
Edit Existing
- Changes to existing parks, rides, or other content
- Shows diff of proposed changes
- Requires source verification
-
Create New
- New park, ride, or content submissions
- Requires complete information
- Needs source verification
Review Process
-
Initial Assessment
- Check submission completeness
- Verify sources
- Review user history
-
Status Options
STATUS_CHOICES = [ ('NEW', 'New'), ('APPROVED', 'Approved'), ('REJECTED', 'Rejected'), ('ESCALATED', 'Escalated'), ] -
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
-
Initial Check
- Image quality
- Appropriate content
- Copyright concerns
- Metadata accuracy
-
Status Options
STATUS_CHOICES = [ ('NEW', 'New'), ('APPROVED', 'Approved'), ('REJECTED', 'Rejected'), ('AUTO_APPROVED', 'Auto Approved'), ] -
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
-
Content Standards
- Constructive feedback
- No personal attacks
- Family-friendly language
- Factual accuracy
-
Rating Consistency
- Check against written content
- Compare with average ratings
- Look for rating abuse
-
Photo Guidelines
- Relevant to review
- Appropriate content
- Quality standards
Report Handling
-
Review Reports
- Assess reported content
- Check reporter history
- Verify claims
-
Actions
- Remove inappropriate content
- Edit/update if needed
- Notify users
- Document actions
Best Practices
General Guidelines
-
Consistency
- Follow established guidelines
- Apply rules uniformly
- Document decisions
-
Communication
- Clear explanations
- Professional tone
- Constructive feedback
-
Escalation
- Know when to escalate
- Document complex cases
- Seek admin input
Quality Control
-
Content Standards
- Accuracy
- Completeness
- Formatting
- Source verification
-
User Management
- Track user history
- Identify trusted contributors
- Handle problem users
-
Documentation
- Record decisions
- Note special cases
- Track patterns
Moderation Tools
Edit Submission Tools
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
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
-
Handling Conflicts
- Review all perspectives
- Check reliable sources
- Document decisions
- Consider escalation
-
Resolution Process
- Gather evidence
- Consult experts if needed
- Make documented decision
- Communicate clearly
Emergency Situations
-
Immediate Action Needed
- Inappropriate content
- Copyright violations
- Personal information
- Harmful content
-
Response Protocol
- Remove content immediately
- Document action taken
- Notify administrators
- Follow up as needed
Moderation Workflow
-
Daily Tasks
- Review new submissions
- Check reported content
- Handle escalations
- Update documentation
-
Weekly Tasks
- Review moderation patterns
- Check for recurring issues
- Update guidelines if needed
- Team communication
-
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
-
New Moderator Training
- Platform overview
- Tools introduction
- Guidelines review
- Supervised practice
-
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.