mirror of
https://github.com/Monadical-SAS/reflector.git
synced 2025-12-20 12:19:06 +00:00
* feat: calendar integration
* feat: add ICS calendar API endpoints for room configuration and sync
* feat: add Celery background tasks for ICS sync
* feat: implement Phase 2 - Multiple active meetings per room with grace period
This commit adds support for multiple concurrent meetings per room, implementing
grace period logic and improved meeting lifecycle management for calendar integration.
## Database Changes
- Remove unique constraint preventing multiple active meetings per room
- Add last_participant_left_at field to track when meeting becomes empty
- Add grace_period_minutes field (default: 15) for configurable grace period
## Meeting Controller Enhancements
- Add get_all_active_for_room() to retrieve all active meetings for a room
- Add get_active_by_calendar_event() to find meetings by calendar event ID
- Maintain backward compatibility with existing get_active() method
## New API Endpoints
- GET /rooms/{room_name}/meetings/active - List all active meetings
- POST /rooms/{room_name}/meetings/{meeting_id}/join - Join specific meeting
## Meeting Lifecycle Improvements
- 15-minute grace period after last participant leaves
- Automatic reactivation when participant rejoins during grace period
- Force close calendar meetings 30 minutes after scheduled end time
- Update process_meetings task to handle multiple active meetings
## Whereby Integration
- Clear grace period when participants join via webhook events
- Track participant count for grace period management
## Testing
- Add comprehensive tests for multiple active meetings
- Test grace period behavior and participant rejoin scenarios
- Test calendar meeting force closure logic
- All 5 new tests passing
This enables proper calendar integration with overlapping meetings while
preventing accidental meeting closures through the grace period mechanism.
* feat: implement frontend for calendar integration (Phase 3 & 4)
- Created MeetingSelection component for choosing between multiple active meetings
- Shows both active meetings and upcoming calendar events (30 min ahead)
- Displays meeting metadata with privacy controls (owner-only details)
- Supports creation of unscheduled meetings alongside calendar meetings
- Added waiting page for users joining before scheduled start time
- Shows countdown timer until meeting begins
- Auto-transitions to meeting when calendar event becomes active
- Handles early joining with proper routing
- Created collapsible info panel showing meeting details
- Displays calendar metadata (title, description, attendees)
- Shows participant count and duration
- Privacy-aware: sensitive info only visible to room owners
- Integrated ICS settings into room configuration dialog
- Test connection functionality with immediate feedback
- Manual sync trigger with detailed results
- Shows last sync time and ETag for monitoring
- Configurable sync intervals (1 min to 1 hour)
- New /room/{roomName} route for meeting selection
- Waiting room at /room/{roomName}/wait?eventId={id}
- Classic room page at /{roomName} with meeting info
- Uses sessionStorage to pass selected meeting between pages
- Added new endpoints for active/upcoming meetings
- Regenerated TypeScript client with latest OpenAPI spec
- Proper error handling and loading states
- Auto-refresh every 30 seconds for live updates
- Color-coded badges for meeting status
- Attendee status indicators (accepted/declined/tentative)
- Responsive design with Chakra UI components
- Clear visual hierarchy between active and upcoming meetings
- Smart truncation for long attendee lists
This completes the frontend implementation for calendar integration,
enabling users to seamlessly join scheduled meetings from their
calendar applications.
* WIP: Migrate calendar integration frontend to React Query
- Migrate all calendar components from useApi to React Query hooks
- Fix Chakra UI v3 compatibility issues (Card, Progress, spacing props, leftIcon)
- Update backend Meeting model to include calendar fields
- Replace imperative API calls with declarative React Query patterns
- Remove old OpenAPI generated files that conflict with new structure
* fix: alembic migrations
* feat: add calendar migration
* feat: update ics, first version working
* feat: implement tabbed interface for room edit dialog
- Add General, Calendar, and Share tabs to organize room settings
- Move ICS settings to dedicated Calendar tab
- Move Zulip configuration to Share tab
- Keep basic room settings and webhooks in General tab
- Remove redundant migration file
- Fix Chakra UI v3 compatibility issues in calendar components
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* fix: infinite loop
* feat: improve ICS calendar sync UX and fix room URL matching
- Replace "Test Connection" button with "Force Sync" button (Edit Room only)
- Show detailed sync results: total events downloaded vs room matches
- Remove emoticons and auto-hide timeout for cleaner UX
- Fix room URL matching to use UI_BASE_URL instead of BASE_URL
- Replace FaSync icon with LuRefreshCw for consistency
- Clear sync results when dialog closes or Force Sync pressed
- Update tests to reflect UI_BASE_URL change and exact URL matching
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: reorganize room edit dialog and fix Force Sync button
- Move WebHook configuration from General to dedicated WebHook tab
- Add WebHook tab after Share tab in room edit dialog
- Fix Force Sync button not appearing by adding missing isEditing prop
- Fix indentation issues in MeetingSelection component
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: complete calendar integration with UI improvements and code cleanup
Calendar Integration Tasks:
- Update upcoming meetings window from 30 to 120 minutes
- Include currently happening events in upcoming meetings API
- Create shared time utility functions (formatDateTime, formatCountdown, formatStartedAgo)
- Improve ongoing meetings UI logic with proper time detection
- Fix backend code organization and remove excessive documentation
UI/UX Improvements:
- Restructure room page layout using MinimalHeader pattern
- Remove borders from header and footer elements
- Change button text from "Leave Meeting" to "Leave Room"
- Remove "Back to Reflector" footer for cleaner design
- Extract WaitPageClient component for better separation
Backend Changes:
- calendar_events.py: Fix import organization and extend timing window
- rooms.py: Update API default from 30 to 120 minutes
- Enhanced test coverage for ongoing meeting scenarios
Frontend Changes:
- MinimalHeader: Add onLeave prop for custom navigation
- MeetingSelection: Complete layout restructure with shared utilities
- timeUtils: New shared utility file for consistent time formatting
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: remove wait page and simplify Join button with 5-minute disable logic
- Remove entire wait page directory and associated files
- Update handleJoinUpcoming to create unscheduled meeting directly
- Simplify Join button to single state:
- Always shows "Join" text
- Blue when meeting can be joined (ongoing or within 5 minutes)
- Gray/disabled when more than 5 minutes away
- Remove confusing "Join Now", "Join Early" text variations
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: improve calendar integration and meeting UI
- Refactor ICS sync tasks to use @asynctask decorator for cleaner async handling
- Extract meeting creation logic into reusable function
- Improve meeting selection UI with distinct current/upcoming sections
- Add early join functionality for upcoming meetings within 5-minute window
- Simplify non-ICS room workflow with direct Whereby embed
- Fix import paths and component organization
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: restore original recording consent functionality
- Remove custom ConsentDialogButton and WherebyEmbed components
- Merge RoomClient logic back into main room page
- Restore original consent UI: blue button with toast modal
- Maintain calendar integration features for ICS-enabled rooms
- Add consent-handler.md documentation of original functionality
- Preserve focus management and accessibility features
* fix: redirect Join Now button to local meeting page
- Change handleJoinDirect to use onMeetingSelect instead of opening external URL
- Join Now button now navigates to /{roomName}/{meetingId} instead of whereby.com
- Maintains proper routing within the application
* feat: remove restrictive message for non-owners in private rooms
- Remove confusing message about room owner permissions
- Cleaner UI for all users regardless of ownership status
- Users will only see available meetings and join options
* feat: improve meeting selection UI for better readability
- Limit page content to max 800px width for better 4K display readability
- Remove LIVE tag badge for cleaner interface
- Remove shadow from main live meeting box
- Remove blue border and hover effects for minimal design
- Change background to neutral gray for less visual noise
* feat: add room by name endpoint for non-authenticated access
- Add GET /rooms/name/{room_name} backend endpoint
- Endpoint supports non-authenticated access for public rooms
- Returns RoomDetails with webhook fields hidden for non-owners
- Update useRoomGetByName hook to use new direct endpoint
- Remove authentication requirement from frontend hook
- Regenerate API client types
Fixes: Non-authenticated users can now access room lobbies
* feat: add friendly message when no meetings are ongoing
- Show centered message with calendar icon when no meetings are active
- Message text: 'No meetings right now' with helpful description
- Contextual text for owners/shared rooms mentioning quick meeting option
- Consistent gray styling matching the rest of the interface
- Only displays when both currentMeetings and upcomingMeetings are empty
* style: center no meetings message and remove background
- Change from Box to Flex with flex=1 for vertical centering
- Remove gray background, border radius, and padding
- Message now appears cleanly centered in available space
- Maintains horizontal and vertical centering
* feat: move Create Meeting button to header
- Remove 'Start a Quick Meeting' box from main content area
- Add showCreateButton and onCreateMeeting props to MinimalHeader
- Create Meeting button now appears in header left of Leave Room
- Only shows for room owners or shared room users
- Update no meetings message to remove reference to quick meeting below
- Cleaner, more accessible UI with actions in the header
* style: change room title and no meetings text to pure black
- Update room title in MinimalHeader from gray.700 to black
- Update 'No meetings right now' text from gray.700 to black
- Improves visual hierarchy and readability
- Consistent with other pages' styling
* style: linting
* fix: remove plan files
* fix: alembic migration with named foreign keys
* feat: add SyncStatus enum and refactor ICS sync to use rooms controller
- Add SyncStatus enum to replace string literals in ICS sync status
- Replace direct SQL queries in worker with rooms_controller.get_ics_enabled()
- Improve type safety and maintainability of ICS sync code
- Enum values: SUCCESS, UNCHANGED, ERROR, SKIPPED maintain backward compatibility
* refactor: remove unnecessary docstring from get_ics_enabled method
The function name is self-explanatory
* fix: import top level
* feat: use Literal type for ICSStatus.status field
- Changed ICSStatus.status from str to Literal['enabled', 'disabled']
- Improves type safety and API documentation
* feat: update TypeScript definitions for ICSStatus Literal type
- OpenAPI generation now properly reflects Literal['enabled', 'disabled'] type
- Improves type safety for frontend consumers of the API
- Applied automatic formatting via pre-commit hooks
* refactor: replace loguru with structlog in ics_sync service
- Replace loguru import with structlog in services/ics_sync.py
- Update logging calls to use structlog's structured format with keyword args
- Maintains consistency with other services using structlog
- Changes: logger.info(f'...') -> logger.info('...', key=value) format
* chore: remove loguru dependency and improve type annotations
- Remove loguru from dependencies in pyproject.toml (replaced with structlog)
- Update meeting controller methods to properly return Optional types
- Update dependency lock file after loguru removal
* fix: resolve pyflakes warnings in ics_sync and meetings modules
Remove unused imports and variables to clean up code quality
* Remove grace period logic and improve meeting deactivation
- Removed grace_period_minutes and last_participant_left_at fields
- Simplified deactivation logic based on actual usage patterns:
* Active sessions: Keep meeting active regardless of scheduled time
* Calendar meetings: Wait until scheduled end if unused, deactivate immediately once used and empty
* On-the-fly meetings: Deactivate immediately when empty
- Created migration to drop unused database columns
- Updated tests to remove grace period test cases
* Update test to match new deactivation logic for calendar meetings
* fix: remove unwanted file
* fix: incompleted changes from EVENT_WINDOW*
* fix: update room ICS API tests to include required webhook fields and correct URL
- Add webhook_url and webhook_secret fields to room creation tests
- Fix room URL matching in ICS sync test to use UI_BASE_URL instead of BASE_URL
- Aligns test with actual API requirements and ICS sync service implementation
* fix: add Redis distributed locking to prevent race conditions in process_meetings
- Implement per-meeting locks using Redis to prevent concurrent processing
- Add lock extension after slow API calls (Whereby) to handle long-running operations
- Use redis-py's built-in lock.extend() with replace_ttl=True for simple TTL refresh
- Track and log skipped meetings when locked by other workers
- Document SSRF analysis showing it's low-risk due to async worker isolation
This prevents multiple workers from processing the same meeting simultaneously,
which could cause state corruption or duplicate deactivations.
* refactor: rename MinimalHeader to MeetingMinimalHeader for clarity
* fix: minor code quality improvements - add emoji constants, fix type safety, cleanup comments
* fix: database migration
* self-pr review
* self-pr review
* self-pr review treeshake
* fix: local fixes
* fix: creation of meeting
* fix: meeting selection create button
* compile fix
* fix: meeting selection responsive
* fix: rework process logic for meeting
* fix: meeting useEffect frontend-only dedupe (#647)
* meeting useEffect frontend-only dedupe
* format
* also get room by name backend fix
---------
Co-authored-by: Igor Loskutov <igor.loskutoff@gmail.com>
* invalidate meeting list on new meeting
* test fix
* room url copy button for ics
* calendar refresh quick action icon
* remove work.md
* meeting page frontend fixes
* hide number of meeting participants
* Revert "hide number of meeting participants"
This reverts commit 38906c5d1a.
* ui bits
* ui bits
* remove log
* room name typing stricten
* feat: protect atomic operation involving external service with redlock
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Igor Monadical <igor@monadical.com>
Co-authored-by: Igor Loskutov <igor.loskutoff@gmail.com>
513 lines
17 KiB
TypeScript
513 lines
17 KiB
TypeScript
"use client";
|
|
import { useEffect, useState, use } from "react";
|
|
import Link from "next/link";
|
|
import Image from "next/image";
|
|
import { notFound } from "next/navigation";
|
|
import useRoomDefaultMeeting from "../../[roomName]/useRoomDefaultMeeting";
|
|
import dynamic from "next/dynamic";
|
|
const WherebyEmbed = dynamic(() => import("../../lib/WherebyWebinarEmbed"), {
|
|
ssr: false,
|
|
});
|
|
import { FormEvent } from "react";
|
|
import { Input, Field } from "@chakra-ui/react";
|
|
import { VStack } from "@chakra-ui/react";
|
|
import { Alert } from "@chakra-ui/react";
|
|
import { Text } from "@chakra-ui/react";
|
|
|
|
type FormData = {
|
|
name: string;
|
|
email: string;
|
|
company: string;
|
|
role: string;
|
|
};
|
|
|
|
const FORM_ID = "1hhtO6x9XacRwSZS-HRBLN9Ca_7iGZVpNX3_EC4I1uzc";
|
|
const FORM_FIELDS = {
|
|
name: "entry.1500809875",
|
|
email: "entry.1359095250",
|
|
company: "entry.1851914159",
|
|
role: "entry.1022377935",
|
|
};
|
|
|
|
export type WebinarDetails = {
|
|
params: Promise<{
|
|
title: string;
|
|
}>;
|
|
};
|
|
|
|
export type Webinar = {
|
|
title: string;
|
|
startsAt: string;
|
|
endsAt: string;
|
|
};
|
|
|
|
enum WebinarStatus {
|
|
Upcoming = "upcoming",
|
|
Live = "live",
|
|
Ended = "ended",
|
|
}
|
|
|
|
const ROOM_NAME = "webinar";
|
|
|
|
const WEBINARS: Webinar[] = [
|
|
{
|
|
title: "ai-operational-assistant",
|
|
startsAt: "2025-02-05T17:00:00Z", // 12pm EST
|
|
endsAt: "2025-02-05T18:00:00Z",
|
|
},
|
|
{
|
|
title: "ai-operational-assistant-dry-run",
|
|
startsAt: "2025-02-05T02:30:00Z",
|
|
endsAt: "2025-02-05T03:10:00Z",
|
|
},
|
|
];
|
|
|
|
export default function WebinarPage(details: WebinarDetails) {
|
|
const params = use(details.params);
|
|
const title = params.title;
|
|
const webinar = WEBINARS.find((webinar) => webinar.title === title);
|
|
if (!webinar) {
|
|
return notFound();
|
|
}
|
|
const startDate = new Date(Date.parse(webinar.startsAt));
|
|
const endDate = new Date(Date.parse(webinar.endsAt));
|
|
|
|
const meeting = useRoomDefaultMeeting(ROOM_NAME);
|
|
const roomUrl = meeting?.response?.host_room_url
|
|
? meeting?.response?.host_room_url
|
|
: meeting?.response?.room_url;
|
|
|
|
const [status, setStatus] = useState(WebinarStatus.Ended);
|
|
const [countdown, setCountdown] = useState({
|
|
days: 0,
|
|
hours: 0,
|
|
minutes: 0,
|
|
seconds: 0,
|
|
});
|
|
|
|
useEffect(() => {
|
|
const updateCountdown = () => {
|
|
const now = new Date();
|
|
|
|
if (now < startDate) {
|
|
setStatus(WebinarStatus.Upcoming);
|
|
const difference = startDate.getTime() - now.getTime();
|
|
setCountdown({
|
|
days: Math.floor(difference / (1000 * 60 * 60 * 24)),
|
|
hours: Math.floor((difference / (1000 * 60 * 60)) % 24),
|
|
minutes: Math.floor((difference / 1000 / 60) % 60),
|
|
seconds: Math.floor((difference / 1000) % 60),
|
|
});
|
|
} else if (now < endDate) {
|
|
setStatus(WebinarStatus.Live);
|
|
}
|
|
};
|
|
|
|
updateCountdown();
|
|
|
|
const timer = setInterval(updateCountdown, 1000);
|
|
return () => clearInterval(timer);
|
|
}, [webinar]);
|
|
|
|
const [formSubmitted, setFormSubmitted] = useState(false);
|
|
const [formData, setFormData] = useState<FormData>({
|
|
name: "",
|
|
email: "",
|
|
company: "",
|
|
role: "",
|
|
});
|
|
|
|
const handleSubmit = async (e: FormEvent) => {
|
|
e.preventDefault();
|
|
|
|
try {
|
|
const submitUrl = `https://docs.google.com/forms/d/${FORM_ID}/formResponse`;
|
|
const data = Object.entries(FORM_FIELDS)
|
|
.map(([key, value]) => {
|
|
return `${value}=${formData[key as keyof FormData]}`;
|
|
})
|
|
.join("&");
|
|
const response = await fetch(submitUrl, {
|
|
method: "POST",
|
|
mode: "no-cors",
|
|
headers: {
|
|
"Content-Type": "application/x-www-form-urlencoded",
|
|
},
|
|
body: data,
|
|
});
|
|
|
|
setFormSubmitted(true);
|
|
} catch (error) {
|
|
console.error("Error submitting form:", error);
|
|
}
|
|
};
|
|
|
|
const handleLeave = () => {
|
|
const now = new Date();
|
|
if (now > endDate) {
|
|
window.location.reload();
|
|
}
|
|
};
|
|
|
|
if (status === WebinarStatus.Live) {
|
|
return (
|
|
<>{roomUrl && <WherebyEmbed roomUrl={roomUrl} onLeave={handleLeave} />}</>
|
|
);
|
|
}
|
|
if (status === WebinarStatus.Ended) {
|
|
return (
|
|
<div className="max-w-4xl mx-auto px-2 py-8 bg-gray-50">
|
|
<div className="bg-white rounded-3xl px-4 md:px-36 py-4 shadow-md mx-auto">
|
|
<Link href="https://www.monadical.com" target="_blank">
|
|
<img
|
|
src="/monadical-black-white 1.svg"
|
|
alt="Monadical Logo"
|
|
className="mx-auto mb-8"
|
|
width={40}
|
|
height={40}
|
|
/>
|
|
</Link>
|
|
<div className="text-center text-sky-600 text-sm font-semibold mb-4">
|
|
FREE RECORDING
|
|
</div>
|
|
|
|
<h1 className="text-center text-4xl md:text-5xl mb-3 leading-tight">
|
|
Building AI-Powered
|
|
<br />
|
|
Operational Assistants
|
|
</h1>
|
|
|
|
<p className="text-center text-gray-600 mb-4">
|
|
From Simple Automation to Strategic Implementation
|
|
</p>
|
|
|
|
<Image
|
|
src="/webinar-preview.png"
|
|
alt="Webinar Preview"
|
|
width={1280}
|
|
height={720}
|
|
className="mx-auto mb-8"
|
|
style={{
|
|
borderRadius: "12px",
|
|
boxShadow: "0px 4px 12px 0px rgba(0, 0, 0, 0.1)",
|
|
}}
|
|
/>
|
|
|
|
<div className="px-6 md:px-16">
|
|
<button
|
|
onClick={() =>
|
|
window.scrollTo({
|
|
top: document.body.scrollHeight,
|
|
behavior: "smooth",
|
|
})
|
|
}
|
|
className="block w-full max-w-xs mx-auto py-4 px-6 bg-sky-600 text-white text-center font-semibold rounded-full hover:bg-sky-700 transition-colors mb-8 uppercase"
|
|
>
|
|
Get instant access
|
|
</button>
|
|
|
|
<div className="space-y-4 mb-8 mt-24">
|
|
<p>
|
|
The hype around Al agents might be a little premature. But
|
|
operational assistants are very real, available today, and can
|
|
unlock your team to do their best work.
|
|
</p>
|
|
<p>
|
|
In this session,{" "}
|
|
<Link
|
|
href="https://www.monadical.com"
|
|
target="_blank"
|
|
className="text-sky-600 hover:text-sky-700"
|
|
>
|
|
Monadical
|
|
</Link>{" "}
|
|
cofounder Max McCrea dives into what operational assistants are
|
|
and how you can implement them in your organization to deliver
|
|
real, tangible value.
|
|
</p>
|
|
</div>
|
|
|
|
<div className="mb-8">
|
|
<h2 className="font-bold text-xl mb-4">What We Cover:</h2>
|
|
<ul className="space-y-4">
|
|
{[
|
|
"What an AI operational assistant is (and isn't).",
|
|
"Example use cases for how they can be implemented across your organization.",
|
|
"Key security and design considerations to avoid sharing sensitive data with outside platforms.",
|
|
"Live demos showing both entry-level and advanced implementations.",
|
|
"How you can start implementing them to immediately unlock value.",
|
|
].map((item, index) => (
|
|
<li
|
|
key={index}
|
|
className="pl-6 relative before:content-[''] before:absolute before:left-0 before:top-2 before:w-2 before:h-2 before:bg-sky-600"
|
|
>
|
|
{item}
|
|
</li>
|
|
))}
|
|
</ul>
|
|
</div>
|
|
|
|
<p className="mb-8">
|
|
You'll walk away with a clear understanding of how to implement Al
|
|
solutions in your organization, with several demos of actual
|
|
implementations.
|
|
</p>
|
|
|
|
<div className="mb-8">
|
|
<h2 className="font-bold text-xl mb-4">
|
|
To Watch This Webinar, Fill Out the Brief Form Below:
|
|
</h2>
|
|
|
|
{formSubmitted ? (
|
|
<Alert.Root status="success" borderRadius="lg" mb={4}>
|
|
<Alert.Indicator />
|
|
<Alert.Title>
|
|
Thanks for signing up! The webinar recording will be ready
|
|
soon, and we'll email you as soon as it's available. Stay
|
|
tuned!
|
|
</Alert.Title>
|
|
</Alert.Root>
|
|
) : (
|
|
<form onSubmit={handleSubmit}>
|
|
<VStack gap={4} w="full">
|
|
<Field.Root required>
|
|
<Input
|
|
type="text"
|
|
placeholder="Your Name"
|
|
py={4}
|
|
size="md"
|
|
value={formData.name}
|
|
onChange={(e) =>
|
|
setFormData({ ...formData, name: e.target.value })
|
|
}
|
|
/>
|
|
</Field.Root>
|
|
<Field.Root required>
|
|
<Input
|
|
type="email"
|
|
placeholder="Your Email"
|
|
py={4}
|
|
size="md"
|
|
value={formData.email}
|
|
onChange={(e) =>
|
|
setFormData({ ...formData, email: e.target.value })
|
|
}
|
|
/>
|
|
</Field.Root>
|
|
<Input
|
|
type="text"
|
|
placeholder="Company Name"
|
|
py={4}
|
|
size="md"
|
|
value={formData.company}
|
|
onChange={(e) =>
|
|
setFormData({ ...formData, company: e.target.value })
|
|
}
|
|
/>
|
|
<Input
|
|
type="text"
|
|
placeholder="Your Role"
|
|
py={4}
|
|
size="md"
|
|
value={formData.role}
|
|
onChange={(e) =>
|
|
setFormData({ ...formData, role: e.target.value })
|
|
}
|
|
/>
|
|
<button
|
|
type="submit"
|
|
className="block w-full max-w-xs mx-auto py-4 px-6 bg-sky-600 text-white text-center font-semibold rounded-full hover:bg-sky-700 transition-colors uppercase"
|
|
>
|
|
Get instant access
|
|
</button>
|
|
</VStack>
|
|
</form>
|
|
)}
|
|
</div>
|
|
</div>
|
|
<div className="text-center text-gray-600 text-sm my-24">
|
|
POWERED BY:
|
|
<br />
|
|
<Link href="#" className="flex justify-center items-center mx-auto">
|
|
<Image
|
|
src="/reach.svg"
|
|
width={32}
|
|
height={40}
|
|
className="h-11 w-auto"
|
|
alt="Reflector"
|
|
/>
|
|
<div className="flex-col ml-3 mt-4">
|
|
<h1 className="text-[28px] font-semibold leading-tight text-left">
|
|
Reflector
|
|
</h1>
|
|
<p className="text-gray-500 text-xs tracking-tight -mt-1">
|
|
Capture the signal, not the noise
|
|
</p>
|
|
</div>
|
|
</Link>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|
|
|
|
return (
|
|
<div className="max-w-4xl mx-auto px-2 py-8 bg-gray-50">
|
|
<div className="bg-white rounded-3xl px-4 md:px-36 py-4 shadow-md mx-auto">
|
|
<Link href="https://www.monadical.com" target="_blank">
|
|
<img
|
|
src="/monadical-black-white 1.svg"
|
|
alt="Monadical Logo"
|
|
className="mx-auto mb-8"
|
|
width={40}
|
|
height={40}
|
|
/>
|
|
</Link>
|
|
<div className="text-center text-sky-600 text-sm font-semibold mb-4">
|
|
FREE WEBINAR
|
|
</div>
|
|
|
|
<h1 className="text-center text-4xl md:text-5xl mb-3 leading-tight">
|
|
Building AI-Powered
|
|
<br />
|
|
Operational Assistants
|
|
</h1>
|
|
|
|
<p className="text-center text-gray-600 mb-4">
|
|
From Simple Automation to Strategic Implementation
|
|
</p>
|
|
|
|
<p className="text-center font-semibold mb-4">
|
|
Wednesday, February 5th @ 12pm EST
|
|
</p>
|
|
|
|
<div className="flex justify-center gap-1 md:gap-8 mb-8">
|
|
{[
|
|
{ value: countdown.days, label: "DAYS" },
|
|
{ value: countdown.hours, label: "HOURS" },
|
|
{ value: countdown.minutes, label: "MINUTES" },
|
|
{ value: countdown.seconds, label: "SECONDS" },
|
|
].map((item, index) => (
|
|
<div
|
|
key={index}
|
|
className="text-center bg-white border border-gray-100 shadow-md rounded-lg p-4 aspect-square w-24"
|
|
>
|
|
<div className="text-5xl mb-2">{item.value}</div>
|
|
<div className="text-sky-600 text-xs">{item.label}</div>
|
|
</div>
|
|
))}
|
|
</div>
|
|
|
|
<div className="px-6 md:px-16">
|
|
<Link
|
|
href="https://www.linkedin.com/events/7286034395642179584/"
|
|
target="_blank"
|
|
className="block w-full max-w-xs mx-auto py-4 px-6 bg-sky-600 text-white text-center font-semibold rounded-full hover:bg-sky-700 transition-colors mb-8"
|
|
>
|
|
RSVP HERE
|
|
</Link>
|
|
|
|
<div className="space-y-4 mb-8 mt-24">
|
|
<p>
|
|
AI is ready to deliver value to your organization, but it's not
|
|
ready to act autonomously. The highest-value applications of AI
|
|
today are assistants, which significantly increase the efficiency
|
|
of workers in operational roles. Software companies are reporting
|
|
30% improvements in developer output across the board, and there's
|
|
no reason AI can't deliver the same kind of value to workers in
|
|
other roles.
|
|
</p>
|
|
<p>
|
|
In this session,{" "}
|
|
<Link
|
|
href="https://www.monadical.com"
|
|
target="_blank"
|
|
className="text-sky-600 hover:text-sky-700"
|
|
>
|
|
Monadical
|
|
</Link>{" "}
|
|
cofounder Max McCrea will dive into what operational assistants
|
|
are and how you can implement them in your organization to deliver
|
|
real, tangible value.
|
|
</p>
|
|
</div>
|
|
|
|
<div className="mb-8">
|
|
<h2 className="font-bold text-xl mb-4">What We'll Cover:</h2>
|
|
<ul className="space-y-4">
|
|
{[
|
|
"What an AI operational assistant is (and isn't).",
|
|
"Example use cases for how they can be implemented across your organization.",
|
|
"Key security and design considerations to avoid sharing sensitive data with outside platforms.",
|
|
"Live demos showing both entry-level and advanced implementations.",
|
|
"How you can start implementing them to immediately unlock value.",
|
|
].map((item, index) => (
|
|
<li
|
|
key={index}
|
|
className="pl-6 relative before:content-[''] before:absolute before:left-0 before:top-2 before:w-2 before:h-2 before:bg-sky-600"
|
|
>
|
|
{item}
|
|
</li>
|
|
))}
|
|
</ul>
|
|
</div>
|
|
|
|
<div className="mb-8">
|
|
<h2 className="font-bold text-xl mb-4">Who Should Attend:</h2>
|
|
<ul className="space-y-4">
|
|
{[
|
|
"Operations leaders looking to reduce manual work",
|
|
"Technical decision makers evaluating AI solutions",
|
|
"Teams concerned about data security and control",
|
|
].map((item, index) => (
|
|
<li
|
|
key={index}
|
|
className="pl-6 relative before:content-[''] before:absolute before:left-0 before:top-2 before:w-2 before:h-2 before:bg-sky-600"
|
|
>
|
|
{item}
|
|
</li>
|
|
))}
|
|
</ul>
|
|
</div>
|
|
|
|
<p className="mb-8">
|
|
Plan to walk away with a clear understanding of how to implement AI
|
|
solutions in your organization, with live demos of actual
|
|
implementations and plenty of time for Q&A to address your specific
|
|
challenges.
|
|
</p>
|
|
|
|
<Link
|
|
href="https://www.linkedin.com/events/7286034395642179584/"
|
|
target="_blank"
|
|
className="block w-full max-w-xs mx-auto py-4 px-6 bg-sky-600 text-white text-center font-semibold rounded-full hover:bg-sky-700 transition-colors mb-8"
|
|
>
|
|
RSVP HERE
|
|
</Link>
|
|
</div>
|
|
<div className="text-center text-gray-600 text-sm my-24">
|
|
POWERED BY:
|
|
<br />
|
|
<Link href="#" className="flex justify-center items-center mx-auto">
|
|
<Image
|
|
src="/reach.svg"
|
|
width={32}
|
|
height={40}
|
|
className="h-11 w-auto"
|
|
alt="Reflector"
|
|
/>
|
|
<div className="flex-col ml-3 mt-4">
|
|
<h1 className="text-[28px] font-semibold leading-tight text-left">
|
|
Reflector
|
|
</h1>
|
|
<p className="text-gray-500 text-xs tracking-tight -mt-1">
|
|
Capture the signal, not the noise
|
|
</p>
|
|
</div>
|
|
</Link>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
);
|
|
}
|