Event Planning Hub

@sites Build and deploy an internal, workspace-authenticated Event Planning Hub for our company. Make it available to everyone in the workspace.

Use connected company sources to make the app feel grounded in the organization:
- Google Calendar: identify relevant planned event dates and avoid scheduling conflicts.
- Slack: find event-planning channels and recent planning updates.
- Google Drive: link briefs, budgets, run-of-show documents, and event assets.
- Notion: surface event policies, approval guidance, and reusable playbooks.
- If a connected source does not contain useful results, use realistic seeded examples and keep the source references configurable. Do not expose unrelated or sensitive workspace content.

Build an event intake workflow available to all workspace users. The intake form should include:
- Event title
- Event type
- Audience
- Assigned owner
- Objective
- Date range
- Location or virtual format
- Budget
- Expected headcount
- Vendors
- Policy needs
- Notes and relevant resource links

Permissions:
- Any workspace user can submit an intake request.
- Only the assigned event owner can accept or reject the request.
- Enforce owner-only acceptance server-side, not only in the interface.

Create separate views for:
- Overview dashboard
- Active intake requests
- Upcoming events
- Past events
- Templates
- Policies and playbooks

Allow users to duplicate a past event or start from templates such as:
- Meetup
- Customer dinner
- Webinar
- Recruiting event
- Team offsite

Each event detail page should include:
- Event health summary with clear status signals
- Timeline and milestones
- Tasks and owners
- Resource links from Drive, Slack, Notion, and Calendar
- Approval status
- Owner comments
- Policy checklist
- Activity updates

Include policy checklist items for:
- General approvals
- Accessibility
- Swag
- Vendor review
- Privacy
- Communications

Use D1 as the authoritative data store for:
- Event records
- Intake status
- Approvals
- Template metadata
- Tasks and task status
- Policy checklist progress
- Resource links
- Comments

Use R2 only if real file uploads are implemented. Otherwise, store Google Drive references rather than duplicating files.

Design direction:
- Make the interface feel like an operations command center for event owners.
- Use a modern, elevated dashboard style with a dark navigation sidebar, a light content canvas, polished cards, strong information hierarchy, and joyful accent colors.
- Prioritize quick scanning: show pending approvals, policy readiness, upcoming milestones, scheduling conflicts, event health, and recent planning activity prominently.
- Use realistic company-specific examples derived from the connected sources when appropriate.

Before deployment:
- Verify that the production build succeeds.
- Perform a visual review of the dashboard, intake flow, event detail view, and responsive layout.
- Deploy with workspace-wide access.