Tips and Best Practices

Best Practices for Event Descriptions

Writing effective descriptions:

• Be specific: Include unique details about what makes the event special
• Include practical information: Date, time, location, admission, what to bring
• Use keywords naturally: Include terms people might search for
• Tell a story: Help visitors understand what to expect
• Keep it readable: Use short paragraphs and bullet points for easy scanning
• Update regularly: Keep information current, especially for recurring events

Content structure:

1. Opening hook (what makes it special)
2. Key details (date, time, location, admission)
3. What to expect
4. How to participate or attend
5. Contact information

Image Recommendations

Main Image:

• Size: At least 1040x585 pixels (or similar 16:9 aspect ratio)
• Content: Best representation of the event
• Quality: High resolution, well-lit, in focus
• Format: JPG or PNG

Header Image:

• Size: 1920x600 pixels or similar wide format
• Content: Scenic view, venue, or representative scene
• Quality: High resolution, professional if possible
• Format: JPG

Gallery Images:

• Size: 1200x800 pixels or larger
• Content: Variety of views, venue, activities, performers
• Quantity: 5-10 images is ideal
• Quality: Consistent quality and style

General tips:

• Use original photos when possible
• Ensure proper lighting
• Include people when appropriate (shows activity and scale)
• Show different angles and perspectives
• Keep file sizes reasonable for web (optimize before uploading)

Category Organization Tips

Creating an effective category structure:

• Keep it simple: Create 5-10 main categories
• Use clear names: Category names should be immediately understandable
• Consider your audience: Organize in a way that makes sense to your visitors
• Review regularly: Refine your structure as you add more events

Common mistakes to avoid:

• Creating too many categories
• Using vague or unclear category names
• Creating categories for only one or two events
• Not reviewing and consolidating similar categories

Recurring Events Best Practices

Setting up recurring events:

• Test the pattern: Create a test event and verify the recurrence generates correctly
• Set end dates: Always set an end date for recurring events to prevent infinite generation
• Use appropriate patterns: Choose the simplest pattern that works (weekly is often better than daily)
• Document exceptions: Note any dates when recurring events won't occur

Managing recurring events:

• Edit the master: Always edit the master event, not individual instances
• Plan ahead: Recurring events generate up to 180 days in advance
• Monitor end dates: Ensure end dates are appropriate for the event type
• Consider one-time changes: For special cases, you may need to create separate one-time events

SEO Tips

Optimizing for search engines:

• Use descriptive titles: Event titles should be clear and include location when relevant
• Write unique descriptions: Avoid duplicate content across events
• Use meta titles and descriptions: Fill these in for better search engine visibility
• Include location keywords: Naturally include city, region, and area names
• Use proper headings: Structure content with headings when using rich text
• Optimize images: Use descriptive alt text for images
• Create quality content: Search engines favor comprehensive, useful content

Meta title best practices:

• Keep under 60 characters
• Include event name, date, and location when possible
• Make it compelling and descriptive

Meta description best practices:

• Keep under 160 characters
• Summarize what makes the event special
• Include key details (date, location) when space allows

Performance Considerations

For content managers:

• Optimize images before uploading: Compress images to reduce file size
• Use appropriate image sizes: Don't upload unnecessarily large images
• Limit gallery images: While you can add many images, 10-15 is usually sufficient
• Keep descriptions concise: While detailed descriptions are good, extremely long content can impact performance

For API consumers:

• Use appropriate limits: Don't request more data than you need
• Use date filters: Filter by date range to reduce result sets
• Cache responses: API responses are cached, but implement client-side caching too
• Use search filters: Filter results on the server rather than loading everything
• Request only needed fields: The API returns comprehensive data, but you may not need everything

For recurring events:

• Set appropriate end dates: Don't create recurring events that extend too far into the future
• Be mindful of generation: Recurring events generate instances dynamically, which can impact performance with very large date ranges
• Use date filters: Always use date filters when searching to limit recurring event generation

General tips:

• Regularly review and update content to keep it fresh
• Remove outdated or irrelevant events
• Archive old events rather than deleting if you might need the data later
• Monitor API usage and optimize queries as needed