Implement Sponsor Communication System for Admins

[DiegoPisa2003]

Overview

Currently, there's no way for admins to communicate directly with sponsors to request missing data, images, or other information. This feature could improve the quality and completeness of sponsor information in RubyEvents.

Note: This idea originated from a discussion between @marcoroth and @brauliomartinezlm in PR #844, where they identified the need for better alternatives to handle missing sponsor logos and assets.

Sponsors are external brands that may want to review how they're being represented on the platform. This creates a unique opportunity for professional, branded communication that maintains RubyEvents' reputation while engaging with external stakeholders.

Proposed Solution

Implement a comprehensive sponsor communication system that allows admins to:

• Select what type of data/images to request
• Send professional, branded emails directly to sponsors
• Track communication history and status
• Ask sponsors to review and request changes to their displayed information

Feature ideas just to clarify the idea (it does not have to be like this)

1. Admin Interface

• Action Button: Add "Contact Sponsor" action in Avo admin panel for each sponsor
• Request Form: Dropdown to select request type (logo, banner, description, etc.)
• Custom Message: Text area for personalized message
• Email Field: Input for sponsor's contact email (with validation)

2. Email Template

The email may include:

• Professional Header: RubyEvents branding and explanation
• Context Section: Why the sponsor is listed and what RubyEvents is
• Direct Links:
  • Link to sponsor's show page on RubyEvents
  • Link to an event where they sponsored (for visual context)
• Request Details: What specific data/images are needed
• Review Section: Invitation to review current information and request changes

3. Communication Tracking

• Database Model: Store all communication attempts and responses
• Status Tracking: Pending, sent, delivered, read, responded
• History View: Admins can see all previous communications with each sponsor

Benefits

For Admins

• Efficiency: No manual email hunting or external communication
• Professionalism: Consistent, branded communication templates
• Data Accuracy: Sponsors can help maintain accurate information

For Sponsors

• Clear Context: Understanding of why they're listed and what RubyEvents is
• Visual Reference: See how they're currently represented
• Easy Response: Clear instructions on what's asked
• Control: Ability to review and update their information
• Engagement: Active participation in how they're represented

For RubyEvents

• Data Quality: More complete and accurate sponsor profiles
• Community Building: Better relationships with sponsors
• Content Enrichment: Higher quality images and descriptions
• Trust: Sponsors feel more invested and represented accurately
• Reduced Maintenance: Sponsors help keep their information current

[adrienpoly]

Thanks for this detailed description.

I’m not sure we want to go as far as adding a full messaging system to our app at this stage. I haven’t really discussed this with Marco yet, and he may have a different perspective, but my sense is that we should start with something simpler.

Marco has already built a page to select the logo and adjust the page branding. A good first step might be to allow certain approved users to access this page. For example, each sponsor could request access to manage their page. They would authenticate via GitHub OAuth, and if the user belongs to the correct organization, we could then grant them edit permissions.