Eventastic — Development

Eventastic — Project Dashboard

Eventastic — Project Dashboard

PROJECT STATUS: Phase 0 — Foundation & Architecture

CODENAME: Eventastic (temporary, unbranded)

SITE: eventastic.noveltynook.shop

VERSION 3: PAUSED and completely separate.

Project Rule

This dashboard is the operational source of truth. Every task has an ID, status, owner and acceptance criteria. Do not change locked architecture or completed work without explicit approval.

Status Legend

⬜ Not Started   🔄 In Progress   ✅ Done   ⛔ Blocked   🔒 Locked

Phase 0 — Foundation & Architecture

  • 0.01 — Temporary project codename confirmed — ✅ Done
  • 0.02 — Fresh isolated subdomain created — ✅ Done
  • 0.03 — Separate document root verified — ✅ Done
  • 0.04 — Fresh WordPress installation — ✅ Done
  • 0.05 — WPWriter connected to Eventastic — ✅ Done
  • 0.06 — Master strategic blueprint created — ✅ Done
  • 0.07 — Operational project dashboard created — ✅ Done
  • 0.08 — Clean-site baseline verification — 🔄 In Progress (13 active plugins audited; Yoast SEO installed; search engines are hidden; WPWriter attempted Asia/Karachi but WordPress still reports UTC; permalinks remain Plain and must be changed before launch)
  • 0.09 — Backup/restore point verified — ⬜
  • 0.10 — Core plugin compatibility lab — 🔄 In Progress (12 active plugins audited. WooCommerce + Venuera + Expo Booth Booking are primary; WP Event Manager is the primary organizer/event-directory candidate; WCFM remains optional. Yoast SEO is now installed. No further plugins will be added without a demonstrated requirement.)
  • 0.11 — Ticket → payment → QR → check-in proof of concept — ✅ Done (checkout, temporary COD order, confirmation, PDF ticket, QR generation, attendee record and manual check-in VERIFIED; dedicated scanner app is optional paid add-on and is not required for MVP)
  • 0.12 — Stall map → hold → payment → sold proof of concept — ✅ Done (Expo Booth Booking is the locked primary stall engine for MVP; project owner independently tested the complete booking flow successfully. Official documentation confirms interactive map, WooCommerce stock, temporary reservations, abandoned-cart release, manual admin booking and double-booking protection.)
  • 0.13 — Double-booking/concurrency test — ⬜
  • 0.14 — Refund/cancellation inventory test — ⬜
  • 0.15 — Payment architecture decision — ⬜
  • 0.16 — Architecture freeze — ⬜

Phase 1 — Product & UX

  • 1.01 — Product requirements locked — ⬜
  • 1.02 — User journeys — ⬜
  • 1.03 — Sitemap — ⬜
  • 1.04 — Design system — ⬜
  • 1.05 — Homepage — ⬜
  • 1.06 — Event discovery — ⬜
  • 1.07 — Event detail — ⬜
  • 1.08 — Organizer UX — ⬜
  • 1.09 — Ticket UX — ⬜
  • 1.10 — Stall-map UX — ⬜

Phase 2 — Event Directory

  • 2.01 — Event data structure — ⬜
  • 2.02 — Cities/categories — ⬜
  • 2.03 — Search/filter — ⬜
  • 2.04 — Venues — ⬜
  • 2.05 — Frontend event submission — 🔄 In Progress (WP Event Manager frontend submission capability confirmed; dedicated draft page created for

    Event Details

    Maximum file size: 2 GB.
    Attendee will register through email ID or external website.

    )
  • 2.06 — Organizer approval workflow — 🔄 In Progress (WP Event Manager supports account-required submission, role-based submission permissions, admin moderation, pending edits and frontend organizer dashboards; WCFM remains optional commerce infrastructure, not the organizer-control layer.)

Phase 3 — Ticketing

  • 3.01 — Ticket types/inventory — ✅ Done (Venuera ticket product and capacity verified)
  • 3.02 — Checkout/payment — 🔄 In Progress (checkout and temporary COD order verified; final Pakistan payment architecture pending)
  • 3.03 — QR/PDF tickets — ✅ Done (PDF download and QR generation verified)
  • 3.04 — Transaction emails — ⬜
  • 3.05 — Attendee management — 🔄 In Progress (attendee name/email captured; full management workflow pending)
  • 3.06 — QR check-in — 🔄 In Progress (manual Venuera check-in VERIFIED; dedicated camera/scanner app is an optional paid add-on and is not required for MVP)
  • 3.07 — Refund/cancellation rules — ⬜

Phase 4 — Exhibition & Stall Engine

  • 4.01 — Venue/hall model — ⬜
  • 4.02 — Floor-plan builder — ⬜
  • 4.03 — Stall inventory model — ⬜
  • 4.04 — Interactive stall selection — ⬜
  • 4.05 — Temporary holds — ⬜
  • 4.06 — Automated sold/available states — ⬜
  • 4.07 — Stall payment — ⬜
  • 4.08 — Concurrency/double-booking protection — ⬜

Phase 5 — Business Engine

  • 5.01 — Commission model — ⬜
  • 5.02 — Organizer reporting — ⬜
  • 5.03 — Settlement workflow — ⬜
  • 5.04 — Featured events — ⬜
  • 5.05 — Promotions/coupons — ⬜

Phase 6 — Marketing & Analytics

  • 6.01 — GA4 — ⬜
  • 6.02 — Search Console — ⬜
  • 6.03 — Google Ads — ⬜
  • 6.04 — Meta Pixel/CAPI — ⬜
  • 6.05 — TikTok Pixel — ⬜
  • 6.06 — GTM/data layer — ⬜
  • 6.07 — Clarity — ⬜
  • 6.08 — Conversion event taxonomy — ⬜

Phase 7 — Security, QA & Launch

  • 7.01 — Roles/permissions — ⬜
  • 7.02 — Security baseline — ⬜
  • 7.03 — Backups/recovery test — ⬜
  • 7.04 — Mobile QA — ⬜
  • 7.05 — Checkout failure QA — ⬜
  • 7.06 — Double-booking QA — ⬜
  • 7.07 — QR fraud/reuse QA — ⬜
  • 7.08 — Performance/load testing — ⬜
  • 7.09 — Soft launch — ⬜
  • 7.10 — Public launch — ⬜

Locked Project Boundaries

  • 🔒 noveltynook.shop must remain untouched.
  • 🔒 v2.noveltynook.shop must remain untouched.
  • 🔒 Eventastic has its own WordPress installation, files and database.
  • 🔒 No production architecture changes without testing.
  • 🔒 Do not install plugins merely because they appear useful; compatibility must be proven.

Current Architecture — Provisional

WooCommerce + Venuera + Expo Booth Booking are the current core commerce engines. WP Event Manager is the primary candidate for the event directory and frontend organizer workflow. WCFM is optional and remains under compatibility evaluation; we will not give organizers unrestricted WooCommerce product access unless testing proves it is safe and useful. Live Event Seating Lite remains a fallback. Architecture is NOT locked until compatibility, permissions, payment, refund and concurrency tests pass.

Next Action

Next Action: prove the organizer-control configuration on the live WordPress installation without exposing WooCommerce admin. WP Event Manager supports account-required submission, account creation, selectable submission roles, admin moderation and frontend event dashboards. citeturn4search0turn4search1 The remaining proof requires checking the actual Event Manager settings, then running a two-organizer ownership/isolation test and confirming that organizer users cannot reach WooCommerce administration.

Architecture Decision — Organizer Commerce

  • 🔒 Preferred: Do NOT give event managers unrestricted WooCommerce/WCFM access.
  • 🟢 Organizer layer: WP Event Manager frontend submission/dashboard.
  • 🟢 Ticket layer: Venuera + WooCommerce.
  • 🟢 Stall layer: Expo Booth Booking + WooCommerce.
  • 🟡 WCFM: optional fallback only; retain installed for controlled compatibility testing, but do not make it the business foundation.
  • 🔒 Financial control: Eventastic should centrally control customer orders, refunds, platform commission and organizer settlement unless later testing proves a safer automated marketplace model.

Relationship Model to Prove

Organizer → Event → Ticket/Stall Inventory → WooCommerce Order → Attendee/Exhibitor → Revenue/Settlement

The critical technical requirement is maintaining reliable ownership and attribution between these records without granting organizers access to other organizers’ data. This must be proven before architecture freeze.

Research Verification

WP Event Manager documents frontend event dashboards where organizers can manage their submitted events, plus account-required submissions, account roles, moderation and pending edits. citeturn0search0turn0search1 Venuera documents WooCommerce-native ticket delivery, PDF tickets and unique QR codes. citeturn0search2turn0search4

Current Blockers / Risks

  • ⛔ Organizer-to-ticket/stall attribution still requires implementation/QA.
  • ⛔ Double-booking/concurrency test still required for stalls.
  • ⛔ Refund/cancellation inventory behavior still required.
  • ⛔ Final Pakistan payment architecture still required.
  • ⛔ WordPress timezone remains UTC despite WPWriter attempting Asia/Karachi; host/permissions appear to reject the change and require direct WP-admin verification.
  • ⛔ Live WP Event Manager submission settings and user-role configuration still need direct admin verification before the organizer isolation test can be run.
  • ⛔ Permalinks remain Plain and must be changed before public launch.

Resume Protocol

When resuming, read this dashboard first. Continue from the first incomplete task whose dependencies are satisfied. Do not redo completed tasks unless a QA failure requires it.