GatherPress

Comments

1. 

   Velda

   Apr 29, 2026

   ### **Notes: GatherPress Integration Strategy**

   * Two phases for WordPress.org:
   * Phase 1: Move GatherPress blocks into FSE templates; optimize theme.
   * Phase 2: Build a simple front-end event editor (no Gutenberg required).
   * Goal: Reduce complexity for organizers; SaaS-like flow (Meetup-style).
   * Parallel tracks with Dion:
   * Dion: fast 0.3.4-alpha integration.
   * GP team: deliberate build; merge/replace as needed.

   ### **Theme Development Focus**

   * Clean up existing [gatherpress.org](http://gatherpress.org/) theme
   * Move all GatherPress blocks to FSE templates
   * Remove blocks from post content entirely
   * Improve presentation: homepage, event pages, venue pages
   * Target: showcase theme highlighting GatherPress features
   * Similar to annual WordPress themes (2024, 2025\)
   * Demonstrate best practices for GatherPress implementation
   * Design goal: match quality of Luma/Meetup event presentation

   ### **Technical Implementation**

   * Step 1: Template-based block system
   * All RSVP, upcoming/past event blocks in templates
   * Users only add event description and metadata
   * Consistent layout across all events
   * Step 2: Custom admin interface
   * Front-end event creation page
   * Simple form fields: date, time, venue selection
   * No Gutenberg complexity for organizers
   * Rich text editor for descriptions (initially)

   ### **Next Steps**

   * Mike: Complete 0.3.4 work, then focus on theme development
   * Patricia: Test theme changes and provide UX feedback
   * Set up dedicated testing environment for theme iterations
   * Consider student involvement for design polish phase
   * Hold off on podcast/media outreach until tangible releases ready