Phase 2 – User Accounts, Event Submissions, and Featured Banner Integration
Budget: $1,000 – $1,200 USD
I run a community event calendar website built with WordPress and The Events Calendar Pro.
Phase 2 will add user accounts and front-end submissions, so organizers can post their own events and (optionally) request featured banner placements. The site is currently functioning, with a single banner currently displayed manually.
Ideal developer should have experience with The Events Calendar Community plugin and be able to structure in a way that is easy to extend to payment integration in Phase 3.
________________________________________
Goals
1. Implement user registration and login system.
2. Enable front-end event submissions using The Events Calendar: Community Events add-on.
3. Build a proper Featured Banner system as a custom post type that integrates with user accounts and admin approvals.
4. Keep the structure ready for Phase 3 (when paid subscriptions will be added).
________________________________________
Key Requirements
1. User Accounts & Permissions
• Standard WordPress user registration and login.
• Roles and permissions set up so approved users can submit and manage their own events (but not publish without approval).
• Ability for admin to grant (and revoke) “pre-approved” status to trusted users.
Subscription Plan Framework (Pre-E-Commerce):
• During registration, users must choose a plan/tier (e.g., Basic, Business, Premium).
• The plan selection will not involve payment yet but should determine user permissions (e.g., number of events, approval workflow).
• The system must store plan data in a way that can later integrate with WooCommerce or MemberPress.
• Each plan should correspond to a unique user role or user meta field.
• Developer must provide documentation describing how these plans are defined and how to add new ones.
• In Phase 3, these plans will be connected to payment and subscription systems, so code must be modular and extensible.
2. Event Submission System
• Front-end event submission form integrated with The Events Calendar.
• Submitted events go into “Pending Review.”
• Admin dashboard filters and approval workflow.
• User dashboard to view/edit their submissions.
3. Featured Banner System
• Create a custom post type (featured_banner) to replace existing banner structure
• Custom fields: image, short text, link, preferred week (can submit two), assigned week, start/end date, approval status.
• Admin approval workflow (Pending → Approved → Published).
• Once approved, auto-publish at a defined time.
• Front-end query to display approved banners during their scheduled week.
• The system should handle multiple banners (which will display on a page-load rotational basis if more than one user requests the same timeslot).
• Admin to set max number of rotating banners per week.
• Structure it so the banner submission form can later be tied to user accounts and payments (Phase 3).
4. Integration
• User accounts, event submissions, and banner submissions all operate under a consistent permission structure.
• Clean, modular code — future developers can easily connect payments.
5. Testing & Documentation
• Ensure events and banners display correctly and don’t conflict.
• Provide a short developer note summarizing custom post types, field names, and template locations
___________
Deliverables
• Fully functional user account system with front-end event submissions.
• Featured Banner CPT with admin approval and date-based display.
• Admin controls for approval and pre-approval.
• Documentation on structure and integration points.
____________
Budget: $1,000-$1,200
(Phase 3 e-commerce/payments will be a separate project.)
Timeline: 8 days
Phase 2 will add user accounts and front-end submissions, so organizers can post their own events and (optionally) request featured banner placements. The site is currently functioning, with a single banner currently displayed manually.
Ideal developer should have experience with The Events Calendar Community plugin and be able to structure in a way that is easy to extend to payment integration in Phase 3.
________________________________________
Goals
1. Implement user registration and login system.
2. Enable front-end event submissions using The Events Calendar: Community Events add-on.
3. Build a proper Featured Banner system as a custom post type that integrates with user accounts and admin approvals.
4. Keep the structure ready for Phase 3 (when paid subscriptions will be added).
________________________________________
Key Requirements
1. User Accounts & Permissions
• Standard WordPress user registration and login.
• Roles and permissions set up so approved users can submit and manage their own events (but not publish without approval).
• Ability for admin to grant (and revoke) “pre-approved” status to trusted users.
Subscription Plan Framework (Pre-E-Commerce):
• During registration, users must choose a plan/tier (e.g., Basic, Business, Premium).
• The plan selection will not involve payment yet but should determine user permissions (e.g., number of events, approval workflow).
• The system must store plan data in a way that can later integrate with WooCommerce or MemberPress.
• Each plan should correspond to a unique user role or user meta field.
• Developer must provide documentation describing how these plans are defined and how to add new ones.
• In Phase 3, these plans will be connected to payment and subscription systems, so code must be modular and extensible.
2. Event Submission System
• Front-end event submission form integrated with The Events Calendar.
• Submitted events go into “Pending Review.”
• Admin dashboard filters and approval workflow.
• User dashboard to view/edit their submissions.
3. Featured Banner System
• Create a custom post type (featured_banner) to replace existing banner structure
• Custom fields: image, short text, link, preferred week (can submit two), assigned week, start/end date, approval status.
• Admin approval workflow (Pending → Approved → Published).
• Once approved, auto-publish at a defined time.
• Front-end query to display approved banners during their scheduled week.
• The system should handle multiple banners (which will display on a page-load rotational basis if more than one user requests the same timeslot).
• Admin to set max number of rotating banners per week.
• Structure it so the banner submission form can later be tied to user accounts and payments (Phase 3).
4. Integration
• User accounts, event submissions, and banner submissions all operate under a consistent permission structure.
• Clean, modular code — future developers can easily connect payments.
5. Testing & Documentation
• Ensure events and banners display correctly and don’t conflict.
• Provide a short developer note summarizing custom post types, field names, and template locations
___________
Deliverables
• Fully functional user account system with front-end event submissions.
• Featured Banner CPT with admin approval and date-based display.
• Admin controls for approval and pre-approval.
• Documentation on structure and integration points.
____________
Budget: $1,000-$1,200
(Phase 3 e-commerce/payments will be a separate project.)
Timeline: 8 days