Social Sharing & Hashtag Generator¶

Overview¶

The Social Sharing Kit helps event hosts generate platform-ready marketing copy—hashtags, captions, story text, email subject lines, and SEO meta—for Instagram, X (Twitter), LinkedIn, Facebook, and WhatsApp. Content is built from your event details and always includes Nigall brand tags #Nigall and #NigallEvents, plus the handle @nigall_events.

When an OpenAI API key is configured on the server, Nigall uses AI to produce tailored copy. Otherwise, a built-in template engine generates professional fallback assets so the feature works in every environment.

Purpose¶

Reduce time spent writing promotional posts across channels, keep brand voice consistent, and give organizers copy-paste assets for launch announcements, reminders, day-of posts, and attendee share prompts.

Who should use it¶

Benefits¶

• One-click generation from live event data (title, date, venue, price, description)
• Tabbed output by platform with Copy buttons
• Optional custom event hashtag included in primary tags
• Cached results saved on the event—no re-generation unless you choose Regenerate
• Brand-compliant defaults even without AI

Navigation path¶

Tip: Open View Event from the edit page. The Social sharing kit appears in the left column when signed in as the event host.

Prerequisites¶

• Event must exist with title, dates, location, and description filled in
• User must be the event host (Event.host)
• No paid module or subscription required—available on all events
• Optional: Server OPENAI_API_KEY for AI-generated copy (see Administrator notes)

Step-by-step instructions¶

Beginner — Generate your first sharing kit¶

1. Sign in as event host.
2. Open your event → View Event (/events/<pk>/<tag>/).
3. Scroll to Social sharing kit (below Survey questions).
4. Optionally enter a Custom event hashtag (e.g., #SummerFest2026). Use camelCase; no spaces.
5. Click Generate.
6. Browse tabs: Hashtags, Instagram, X / Twitter, LinkedIn, Facebook, WhatsApp, Stories, Email & SEO.
7. Click Copy on any block and paste into your social tool or scheduler.

[SCREENSHOT: Social sharing kit panel with Hashtags tab open]

Intermediate — Regenerate after event updates¶

1. Update event title, date, venue, description, or ticket price on Edit Event.
2. Return to event detail → Social sharing kit.
3. Adjust custom hashtag if needed.
4. Click Regenerate to refresh all assets (previous cache is replaced).

Note: Cached assets are stored on the event. If you only change minor copy in the description, regenerate so captions stay accurate.

Advanced — Use outputs in a campaign workflow¶

Append the platform Follow CTA where relevant (e.g., “Follow @nigall_events for more events near you!” on Instagram).

Field descriptions¶

Data sources (automatic)¶

Business rules¶

Validation rules¶

User permissions¶

Workflow¶

Examples¶

Tech meetup: Custom hashtag #AustinDevNight2026. Use X announcement tweet + LinkedIn post for launch; Instagram reminder 7 days before; attendee share caption for community reposts.

Wedding RSVP: Custom hashtag #SmithJonesWedding. WhatsApp Personal invite for family groups; Instagram attendee share for guests posting “I’m going!”

Paid conference: Regenerate after early-bird pricing ends so Ticket price in captions reflects current tiers.

Best practices¶

• Complete About the Event, location, and cover image before generating
• Set Discover visibility and category before public launch (Discover & Visibility)
• Add survey questions first if copy should reference guest data collection (Survey & Custom Questions)
• Regenerate after any date, venue, or pricing change
• Pair kit output with Email Blasts for owned-audience sends
• Use Full tag string for Instagram (hashtags at end of caption per platform norms)

Tips¶

• Status line shows AI vs template source after generation
• LinkedIn posts: keep to ≤5 hashtags for professional tone
• Story overlays are short by design—pair with event cover art in your design tool
• SEO fields are suggestions; paste into meta tags if you customize landing pages externally

Common mistakes¶

FAQs¶

Does Nigall post to Instagram or X for me?
No. The kit generates copy; you publish through each platform or your scheduling tool.

Is AI required?
No. Template fallback produces complete assets without an API key.

Can attendees see the kit?
Hosts see the full Social sharing kit. Guests who RSVP Will Attend / Tentative (or have a confirmed registration) see a Share that you're going panel with attendee captions and hashtags—only after the host has generated the kit once.

Do RSVP and Registration events both support this?
Yes. Ticket price line adapts (Free, RSVP, or priced tiers).

Where are brand hashtags defined?
Always #Nigall and #NigallEvents; handle @nigall_events.

Troubleshooting¶

Related features¶

• Discover & Event Visibility
• Email Communications & Blasts
• Events & Registration
• Survey & Custom Questions
• Field Reference — Event Model

Screenshot placeholders¶

1. [SCREENSHOT: Social sharing kit — custom hashtag + Generate button]
2. [SCREENSHOT: Hashtags tab — primary, secondary, full tag string]
3. [SCREENSHOT: Instagram tab — organizer announcement with Copy button]
4. [SCREENSHOT: Email & SEO tab — subject lines and meta fields]

Administrator notes¶

Environment variables (optional AI):

Prompt template path: events/prompts/social_sharing.txt

Generated JSON stored in Event.social_sharing_assets. No PII beyond event/host display name is sent to OpenAI.

Developer / API notes¶

Endpoint: POST /events/<pk>/<event_tag>/social-sharing/generate/

Body (form-urlencoded):

Response (JSON):

{
  "ok": true,
  "assets": {
    "hashtags": { "primary": [], "secondary": [], "full_tag_string": "" },
    "captions": { "instagram": {}, "x_twitter": {}, "linkedin": {}, "facebook": {}, "whatsapp": {} },
    "story_text": {},
    "email_subject_lines": [],
    "seo_meta": {},
    "follow_cta": {},
    "brand_compliance_check": {},
    "_source": "openai | fallback",
    "generated_at": "ISO-8601 timestamp"
  }
}

Service module: events.social_sharing_services.generate_social_sharing_assets()