\n Rust NYC Talk Submissions\n

\n Submit your talk proposal and get connected with our organizers\n

\n\n {submissionResult ? (\n \n ) : (\n \n )}\n

\n \n );\n}",[],[183,190,197],{"_103":207,"_95":208,"_153":209,"_155":191,"_156":138,"_157":210,"_159":160,"_105":211,"_100":212,"_162":202,"_164":213,"_165":22,"_166":-5,"_167":214,"_98":215},"a03f5bbe-5a82-11f0-bc2c-f69ea79377d9","SubmissionSuccess.tsx","ad61c32e-5107-11f0-b701-f69ea79377d9",67,["D",1751817752842],4,"/** @jsxImportSource https://esm.sh/react@18.2.0 */\nimport React from \"https://esm.sh/react@18.2.0\";\nimport type { SubmissionResult } from \"./App.tsx\";\n\ninterface SubmissionSuccessProps {\n result: SubmissionResult;\n onReset: () => void;\n}\n\nexport default function SubmissionSuccess({ result, onReset }: SubmissionSuccessProps) {\n const copyInviteLink = async () => {\n try {\n await navigator.clipboard.writeText(result.discordInviteLink);\n // Could add a toast notification here\n } catch (err) {\n console.error(\"Failed to copy link:\", err);\n }\n };\n\n return (\n

\n {/* Success Icon */}\n

\n ✓\n

\n\n {/* Success Message */}\n

\n Submission Successful\n

\n Your talk proposal has been submitted and our organizers have been notified.\n

\n\n {/* Submission Details */}\n

\n Submission ID: #{result.submissionId}\n

\n\n {/* Discord Invite Section */}\n

\n 💬\n

\n Discord Discussion Channel\n

\n \n

\n A dedicated Discord channel has been created for discussing your talk proposal.\n Join the conversation with our organizers!\n

\n\n

\n {/* Invite Link Display */}\n

\n \n {result.discordInviteLink}\n \n \n 📋\n \n

\n\n {/* Action Buttons */}\n

\n \n Join Discord Channel\n \n \n Copy Invite Link\n \n

\n\n {/* Next Steps */}\n

What happens next?

• Our organizers have been notified of your submission
• Join the Discord channel to discuss details
• We'll review your proposal and get back to you soon
• Keep an eye on Discord for updates and questions

\n\n {/* Reset Button */}\n \n Submit Another Talk →\n \n

\n );\n}",[],[183,190,208],{"_103":217,"_95":218,"_153":219,"_155":191,"_156":138,"_157":220,"_159":160,"_105":221,"_100":222,"_162":202,"_164":223,"_165":22,"_166":-5,"_167":224,"_98":225},"a033fb66-5a82-11f0-a16c-f69ea79377d9","TalkSubmissionForm.tsx","9d3d85a0-5107-11f0-bdc6-f69ea79377d9",65,["D",1751817752841],7,"/** @jsxImportSource https://esm.sh/react@18.2.0 */\nimport React, { useState } from \"https://esm.sh/react@18.2.0\";\nimport type { SubmissionData } from \"./App.tsx\";\n\ninterface TalkSubmissionFormProps {\n onSubmit: (data: SubmissionData) => void;\n isSubmitting: boolean;\n error: string | null;\n}\n\nexport default function TalkSubmissionForm({ onSubmit, isSubmitting, error }: TalkSubmissionFormProps) {\n const [formData, setFormData] = useState({\n speakerName: \"\",\n talkContext: \"\",\n isOnBehalf: false,\n submitterName: \"\",\n });\n\n const handleSubmit = (e: React.FormEvent) => {\n e.preventDefault();\n \n // Basic validation\n if (!formData.speakerName.trim() || !formData.talkContext.trim()) {\n return;\n }\n\n // Validate submitter name if submitting on behalf\n if (formData.isOnBehalf && !formData.submitterName?.trim()) {\n return;\n }\n\n onSubmit(formData);\n };\n\n const handleInputChange = (field: keyof SubmissionData, value: string | boolean) => {\n setFormData(prev => ({\n ...prev,\n [field]: value\n }));\n };\n\n const isFormValid = formData.speakerName.trim() && \n formData.talkContext.trim() && \n (!formData.isOnBehalf || formData.submitterName?.trim());\n\n return (\n

\n {/* Speaker Name */}\n

\n \n Speaker Name *\n \n handleInputChange(\"speakerName\", e.target.value)}\n className=\"w-full px-3 py-2 border border-[var(--border-default)] rounded bg-white font-mono text-sm focus:outline-none focus:border-[var(--accent-primary)] focus:border-2\"\n placeholder=\"Enter the speaker's full name\"\n disabled={isSubmitting}\n />\n

\n\n {/* Talk Context */}\n

\n \n Talk Context *\n \n handleInputChange(\"talkContext\", e.target.value)}\n className=\"w-full px-3 py-2 border border-[var(--border-default)] rounded bg-white font-mono text-sm focus:outline-none focus:border-[var(--accent-primary)] focus:border-2\"\n placeholder=\"Describe the talk topic, key points, target audience, and any other relevant context...\"\n disabled={isSubmitting}\n />\n

\n\n {/* On Behalf Checkbox */}\n

\n handleInputChange(\"isOnBehalf\", e.target.checked)}\n className=\"w-4 h-4 accent-[var(--accent-primary)] bg-white border-[var(--border-default)] rounded focus:ring-2 focus:ring-[var(--accent-primary)]\"\n disabled={isSubmitting}\n />\n

\n \n I am submitting this on behalf of someone else\n \n

\n Check this if you're not the speaker but are submitting for them\n

\n\n {/* Submitter Name - Only show when submitting on behalf */}\n {formData.isOnBehalf && (\n

\n \n Your Name (Submitter) *\n \n handleInputChange(\"submitterName\", e.target.value)}\n className=\"w-full px-3 py-2 border border-[var(--border-default)] rounded bg-white font-mono text-sm focus:outline-none focus:border-[var(--accent-primary)] focus:border-2\"\n placeholder=\"Enter your full name\"\n disabled={isSubmitting}\n />\n

\n Since you're submitting on behalf of the speaker, please provide your name for our records.\n

\n )}\n\n {/* Error Message */}\n {error && (\n

\n ⚠\n

{error}

\n )}\n\n {/* Submit Button */}\n

\n \n {isSubmitting ? (\n <>\n \n Processing Submission...\n \n ) : (\n \"Submit Talk Proposal\"\n )}\n \n

\n\n

\n After submission, a Discord channel will be created for discussion\n and you'll receive an invitation link.\n

\n );\n}",[],[183,190,218],[183,190],{"_103":228,"_95":229,"_153":230,"_155":184,"_156":138,"_157":185,"_159":160,"_105":231,"_100":32,"_162":232,"_164":233,"_165":22,"_166":-5,"_167":234,"_98":235},"8202ed34-5107-11f0-8db1-f69ea79377d9","index.html","8202ede8-5107-11f0-8db1-f69ea79377d9",["D",1750775313623],"file","\n\n\n \n \n Talk Submission Form\n \n \n\n\n

\n \n\n",[],[183,229],{"_103":237,"_95":238,"_153":239,"_155":184,"_156":138,"_157":240,"_159":160,"_105":241,"_100":158,"_162":202,"_164":242,"_165":22,"_166":-5,"_167":243,"_98":244},"8d7d69c6-5d11-11f0-a6e1-0224a6c84d84","index.tsx","84fc4d46-5107-11f0-8db1-f69ea79377d9",70,["D",1752099041804],"/** @jsxImportSource https://esm.sh/react@18.2.0 */\nimport React from \"https://esm.sh/react@18.2.0\";\nimport { createRoot } from \"https://esm.sh/react-dom@18.2.0/client\";\nimport App from \"./components/App.tsx\";\n\nconst root = createRoot(document.getElementById(\"root\")!);\nroot.render();",[],[183,238],[183],{"_103":247,"_95":248,"_153":249,"_155":-5,"_156":138,"_157":250,"_159":160,"_105":251,"_100":32,"_162":163,"_164":-5,"_165":22,"_166":-5,"_167":252,"_98":262},"b4d16d6c-5107-11f0-b701-f69ea79377d9","shared","488a1fe0-8197-45ca-8f59-d1dadae612bb",9,["D",1750775398865],[253],{"_103":254,"_95":255,"_153":256,"_155":249,"_156":138,"_157":257,"_159":160,"_105":258,"_100":185,"_162":202,"_164":259,"_165":22,"_166":-5,"_167":260,"_98":261},"9f121808-5109-11f0-b85a-f69ea79377d9","types.ts","b4d1690c-5107-11f0-b701-f69ea79377d9",37,["D",1750776221371],"export interface TalkSubmission {\n id: number;\n speaker_name: string;\n talk_context: string;\n is_on_behalf: boolean;\n submitter_name?: string;\n discord_channel_id?: string;\n discord_invite_link?: string;\n created_at: string;\n}\n\nexport interface SubmissionRequest {\n speakerName: string;\n talkContext: string;\n isOnBehalf: boolean;\n submitterName?: string;\n email: string;\n}\n\nexport interface SubmissionResponse {\n success: boolean;\n submissionId: number;\n discordInviteLink: string;\n}\n\nexport interface DiscordConfig {\n botToken: string;\n guildId: string;\n organizersChannelId: string;\n categoryId?: string;\n}",[],[248,255],[248],{"_103":264,"_95":265,"_153":266,"_155":-5,"_156":138,"_157":267,"_159":160,"_105":268,"_100":32,"_162":232,"_164":269,"_165":22,"_166":-5,"_167":270,"_98":271},"3d067f9a-5a74-11f0-98da-f69ea79377d9",".vtignore","3d06804e-5a74-11f0-98da-f69ea79377d9",41,["D",1751811573421],".git\n.vscode\n.cursorrules\n.DS_Store\nnode_modules\nvendor",[],[265],{"_103":273,"_95":274,"_153":275,"_155":-5,"_156":138,"_157":276,"_159":160,"_105":277,"_100":278,"_162":232,"_164":279,"_165":22,"_166":-5,"_167":280,"_98":281},"81bdc070-5a75-11f0-88c7-f69ea79377d9","AGENT.md","3cfa990a-5a74-11f0-b647-f69ea79377d9",44,["D",1751812118275],1,"# Agent Configuration for Talk Submission System\n\n## Commands\n- **No explicit test/lint commands** - Val Town platform handles these automatically\n- **Development**: Val Town auto-deploys on changes, no local build needed\n- **Database**: SQLite migrations run automatically on startup in backend/index.ts\n\n## Architecture\n- **Val Town Project**: Deno-based Discord bot for talk submissions with React frontend\n- **Backend**: Hono API server (backend/index.ts) handling submissions and Discord integration\n- **Frontend**: React 18.2.0 with TypeScript (frontend/index.tsx, components/)\n- **Database**: SQLite with talk submissions table (talk_submissions_3)\n- **Discord Integration**: Bot creates channels, sends notifications, generates invite links\n- **Shared**: TypeScript types and utilities (shared/types.ts)\n\n## Discord API Design Notes\n- **Role Mentions**: Use `<@&ROLE_ID>` format in message content\n- **User Mentions**: Use `<@USER_ID>` format in message content\n- **Channel Mentions**: Use `<#CHANNEL_ID>` format in message content\n- **Special Mentions**: `@everyone` and `@here` work as plain text (no ID needed)\n- **Permissions**: Role must be mentionable OR bot needs \"Mention Everyone\" permission\n\n## Code Style (from .cursorrules)\n- **Language**: TypeScript/TSX with React 18.2.0\n- **Imports**: Use `https://esm.sh` for npm packages, pin React to 18.2.0\n- **Types**: Add TypeScript types for all data structures\n- **Secrets**: Always use environment variables, never hardcode secrets\n- **JSX**: Start React files with `/** @jsxImportSource https://esm.sh/react@18.2.0 */`\n- **Styling**: Default to TailwindCSS via CDN script tag\n- **Error Handling**: Let errors bubble up with context, avoid empty catch blocks\n- **Database**: Change table names (e.g., _3, _4) when modifying schemas instead of ALTER TABLE\n- **Platform**: Use Val Town utils for file operations (readFile, serveFile)\n",[],[274],{"_103":283,"_95":284,"_153":285,"_155":-5,"_156":138,"_157":286,"_159":160,"_105":287,"_100":278,"_162":232,"_164":288,"_165":22,"_166":-5,"_167":289,"_98":290},"8d78359c-5a81-11f0-9588-f69ea79377d9","BRAND_STYLE_GUIDE.md","d91c02ce-5a7e-11f0-a9cd-f69ea79377d9",63,["D",1751817291900],"# Brand Style Guide\n## Rust NYC Discord Bot - Talk Submission System\n\n### Overview\nA nostalgic minimal, slightly technical theme that evokes the feeling of early computing interfaces while maintaining modern usability and accessibility.\n\n### Typography\n- **Headings**: Instrument Serif (Google Web Fonts) - Elegant, slightly humanistic serif for warmth\n- **Body Text**: System monospace stack for technical authenticity\n- **Code/Data**: Monospace for technical content and data display\n\n### Color Palette\n```\n// Primary - Muted technical grays and warm accents\n--bg-primary: #f8f9fa // Soft off-white background\n--bg-secondary: #e9ecef // Subtle gray for cards\n--bg-tertiary: #dee2e6 // Light gray for inputs\n\n--text-primary: #2d3748 // Dark gray for primary text\n--text-secondary: #4a5568 // Medium gray for secondary text\n--text-muted: #718096 // Light gray for muted text\n\n--accent-primary: #d69e2e // Warm amber for primary actions\n--accent-secondary: #b7791f // Darker amber for hover states\n--accent-subtle: #faf089 // Light amber for subtle highlights\n\n--border-default: #cbd5e0 // Default border color\n--border-focus: #d69e2e // Amber focus borders\n\n// Status colors\n--success: #38a169 // Muted green\n--error: #e53e3e // Muted red\n--warning: #dd6b20 // Muted orange\n--info: #3182ce // Muted blue\n```\n\n### Layout & Spacing\n- **Container**: Max-width 480px for mobile-first, intimate feel\n- **Spacing Scale**: 4px base unit (4, 8, 12, 16, 24, 32, 48, 64)\n- **Border Radius**: 4px for subtle roundness\n- **Borders**: 1px solid borders throughout\n\n### Components\n\n#### Cards\n- Background: `--bg-secondary`\n- Border: 1px solid `--border-default`\n- Padding: 24px\n- Border radius: 4px\n- Subtle drop shadow\n\n#### Forms\n- Input borders: 1px solid `--border-default`\n- Focus state: 2px solid `--accent-primary`\n- Monospace font for consistency\n- Generous padding (12px)\n\n#### Buttons\n- Primary: `--accent-primary` background, dark text\n- Secondary: `--bg-tertiary` background, dark text\n- Padding: 12px 24px\n- Border radius: 4px\n- Monospace font\n\n#### Typography Scale\n- H1: 24px / text-2xl (primary headings)\n- H2: 20px / text-xl (section headings) \n- H3: 18px / text-lg (subsection headings)\n- Body: 14px / text-sm (main content)\n- Small: 12px / text-xs (captions, metadata)\n\n**Important**: All headings using Instrument Serif (.font-heading) must be sized at text-2xl (24px) or larger to ensure proper readability and visual hierarchy. The serif font performs best at larger sizes and maintains the technical aesthetic when prominently displayed.\n\n### Design Principles\n1. **Functional Beauty**: Every element serves a purpose\n2. **Technical Authenticity**: Embrace monospace and structured layouts\n3. **Nostalgic Warmth**: Subtle amber accents and serif headings\n4. **Accessibility First**: High contrast, clear focus states\n5. **Mobile Responsive**: Single-column layouts, touch-friendly sizing\n\n### Implementation Notes\n- Use CSS custom properties for consistency\n- Maintain semantic HTML structure\n- Progressive enhancement approach\n- Dark mode consideration for future iterations\n",[],[284],{"_103":292,"_95":99,"_153":293,"_155":-5,"_156":138,"_157":294,"_159":160,"_105":295,"_100":201,"_162":232,"_164":296,"_165":22,"_166":-5,"_167":297,"_98":298},"df34da58-5a7b-11f0-9b63-f69ea79377d9","bfef9cb4-5107-11f0-b497-f69ea79377d9",54,["D",1751814852025],"# Talk Submission System\n\nA complete talk submission system with Discord integration for event organizers.\n\n## Features\n\n- **Talk Submission Form**: Collects speaker name, talk context, and submission type\n- **Discord Integration**: Automatically creates channels and sends notifications\n- **Database Storage**: Tracks all submissions with SQLite\n- **Responsive UI**: Clean, modern interface built with React and TailwindCSS\n\n## How It Works\n\n1. **Form Submission**: Users fill out the talk submission form\n2. **Database Storage**: Submission is saved to SQLite database\n3. **Discord Channel Creation**: A dedicated channel is created for the talk discussion\n4. **Organizer Notification**: A message is posted to the organizers' channel\n5. **Invite Link**: User receives a Discord invite link to join the discussion\n\n## Project Structure\n\n```\n├── backend/\n│ └── index.ts # Main API server with Hono\n├── frontend/\n│ ├── index.html # Main HTML template\n│ ├── index.tsx # React app entry point\n│ └── components/\n│ ├── App.tsx # Main app component\n│ ├── TalkSubmissionForm.tsx # Form component\n│ └── SubmissionSuccess.tsx # Success page component\n├── shared/\n│ └── types.ts # Shared TypeScript types\n└── README.md\n```\n\n## Setup\n\n### Environment Variables\n\nYou'll need to set up the following environment variables for Discord integration:\n\n- `DISCORD_BOT_TOKEN`: Your Discord bot token\n- `DISCORD_GUILD_ID`: Your Discord server ID\n- `DISCORD_ORGANIZERS_CHANNEL_ID`: Channel ID where organizer notifications are sent\n- `DISCORD_CATEGORY_ID` (optional): Category ID for organizing talk channels\n- `DISCORD_TEST_CATEGORY_ID` (optional): Category ID for organizing test channels\n- `DISCORD_TEST_ORGANIZERS_CHANNEL_ID` (optional): Channel ID for test announcements\n\n#### Testing Environment Variables\n\nThe following environment variables are used for testing the Discord integration without affecting production channels:\n\n- `ENABLE_TEST_API`: Set to \"true\" to enable the test API endpoint (required for testing)\n- `DISCORD_TEST_CATEGORY_ID`: Separate category for test channels to keep them organized\n- `DISCORD_TEST_ORGANIZERS_CHANNEL_ID`: Separate channel for test notifications to avoid spamming production organizers\n\n**Testing the Discord Integration:**\n\n```bash\ncurl -X POST https://rustnyc-talks.val.run/api/discord/test \\\n -H \"Content-Type: application/json\" \\\n -d '{\"channelName\": \"my-test-channel\", \"firstMessage\": \"Hello from test endpoint!\"}'\n```\n\n**Parameters:**\n- `channelName` (required): Name for the test channel (will be sanitized for Discord)\n- `firstMessage` (required): First message to send to the channel\n\nThis will create a test channel with the specified name, send the first message, and return an invite link. If test environment variables are configured, it will also notify the test organizers channel.\n\n**Testing Discord Invite Creation Directly:**\n\nYou can also test the Discord invite creation process directly using Discord's API:\n\n```bash\ncurl -X POST https://discord.com/api/v10/channels/CHANNEL_ID/invites \\\n -H \"Authorization: Bot YOUR_BOT_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\n \"max_age\": 0,\n \"max_uses\": 0,\n \"unique\": true\n }'\n```\n\nReplace `CHANNEL_ID` with an existing channel ID and `YOUR_BOT_TOKEN` with your Discord bot token. This matches exactly how the bot creates invitation links internally.\n\n### Discord Bot Setup\n\n1. Create a Discord application at https://discord.com/developers/applications\n2. Create a bot and copy the token\n3. Invite the bot to your server with the following permissions:\n - Manage Channels\n - Send Messages\n - Create Instant Invite\n - View Channels\n\n### Database\n\nThe system uses SQLite with the following schema:\n\n```sql\nCREATE TABLE talk_submissions_1 (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n speaker_name TEXT NOT NULL,\n talk_context TEXT NOT NULL,\n is_on_behalf BOOLEAN NOT NULL,\n discord_channel_id TEXT,\n discord_invite_link TEXT,\n created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n);\n```\n\n## API Endpoints\n\n- `POST /api/submissions` - Submit a new talk proposal\n- `GET /api/submissions` - Get all submissions (admin)\n- `POST /api/discord/test` - Test Discord integration (creates test channel and sends message)\n\n## Discord Integration Status\n\n✅ **Discord integration is fully implemented with comprehensive logging**\n\nThe system will automatically:\n- Create Discord channels for each talk submission\n- Generate invite links for the channels \n- Post notifications to the organizers channel\n\n**Comprehensive Logging**: The system includes detailed logging throughout the Discord integration process:\n- 🔍 Environment variable checks on startup\n- 🎯 API request tracking with submission details\n- 🔧 Discord channel creation with API responses\n- 🔗 Invite link generation with full details\n- 📢 Organizer notifications with message content\n- 💥 Detailed error logging with stack traces and specific Discord error codes\n- 📊 Final result summaries\n\n**Fallback behavior**: If Discord credentials are not provided, the system will use placeholder values and log what would have been done, allowing the form to still function for testing.\n\n**Debugging**: Use the requests tool to view detailed logs of each submission, including all Discord API interactions and any errors that occur.\n\n## Usage\n\n1. Fill out the talk submission form\n2. Submit the form\n3. Receive a Discord invite link\n4. Join the Discord channel to discuss your talk with organizers\n\n## Tech Stack\n\n- **Backend**: Hono (API framework)\n- **Frontend**: React 18.2.0 with TypeScript\n- **Database**: SQLite\n- **Styling**: TailwindCSS\n- **Platform**: Val Town (Deno runtime)",[],[99],{"_103":300,"_95":301,"_153":302,"_155":-5,"_156":138,"_157":303,"_159":160,"_105":304,"_100":32,"_162":232,"_164":305,"_165":22,"_166":-5,"_167":306,"_98":307},"3d0077ee-5a74-11f0-860c-f69ea79377d9","deno.json","3d0078b6-5a74-11f0-860c-f69ea79377d9",40,["D",1751811573448],"{\n \"$schema\": \"https://raw.githubusercontent.com/denoland/deno/348900b8b79f4a434cab4c74b3bc8d4d2fa8ee74/cli/schemas/config-file.v1.json\",\n \"lock\": false,\n \"compilerOptions\": {\n \"noImplicitAny\": false,\n \"strict\": false,\n \"types\": [\n \"https://www.val.town/types/valtown.d.ts\"\n ],\n \"lib\": [\n \"dom\",\n \"dom.iterable\",\n \"dom.asynciterable\",\n \"deno.ns\",\n \"deno.unstable\"\n ]\n },\n \"lint\": {\n \"files\": {\n \"include\": [\n \"deno:/https/esm.town/**/*\"\n ]\n },\n \"rules\": {\n \"exclude\": [\n \"no-explicit-any\"\n ]\n }\n },\n \"node_modules_dir\": false,\n \"experimental\": {\n \"unstable-node-globals\": true,\n \"unstable-temporal\": true,\n \"unstable-worker-options\": true,\n \"unstable-sloppy-imports\": true\n }\n}",[],[301],{"_103":309,"_95":310,"_153":311,"_155":-5,"_156":138,"_157":278,"_159":160,"_105":312,"_100":32,"_162":202,"_164":72,"_165":22,"_166":-5,"_167":313,"_98":314},"240e71f2-4b86-11f0-94fc-76b3cceeab13","main.tsx","240e72a6-4b86-11f0-94fc-76b3cceeab13",["D",1750169995102],[],[310],"files",[150,169,181,188,195,206,216,227,236,246,253,263,272,282,291,299,308],"counts",{"_319":32,"_320":278,"_321":278,"_322":222},"pulls","branches","forks","envVars","contents",[],{"_103":292,"_95":99,"_153":293,"_155":-5,"_156":138,"_157":294,"_159":160,"_105":326,"_100":201,"_162":232,"_164":296,"_165":22,"_166":-5,"_98":327},["D",1751814852025],[99],"upstreamProject","upstreamBranch","emptyEnvVars","isNew","flags",[],"routes/_app.x.$handle.$name.branch.$branch.history_.$",{"_93":94,"_95":96,"_97":43,"_98":99,"_101":336,"_232":341,"_344":345,"_378":379,"_388":-7,"_389":32,"_390":22},{"_103":104,"_95":96,"_105":337,"_107":-5,"_108":22,"_109":110,"_111":-5,"_112":113,"_14":114,"_115":-5,"_116":22,"_117":-5,"_118":32,"_16":119,"_120":121,"_122":121,"_123":124,"_125":124,"_126":124,"_127":121,"_128":121,"_23":338,"_132":339,"_135":340,"_147":22},["D",1750169995086],{"_93":94,"_130":131},{"_93":94,"_134":131},{"_100":137,"_95":43,"_103":138,"_139":104,"_140":-5,"_141":-5,"_142":-5,"_143":-5,"_144":-5,"_145":96,"_146":94},{"_103":292,"_95":99,"_153":293,"_155":-5,"_156":138,"_157":294,"_159":160,"_105":342,"_100":201,"_162":232,"_164":296,"_165":22,"_166":-5,"_98":343},["D",1751814852025],[99],"history",[346,348,353,358,363,368,373],{"_103":292,"_156":138,"_153":293,"_95":99,"_164":296,"_162":232,"_100":201,"_155":-5,"_105":347,"_157":294,"_166":-5},["D",1751814852025],{"_103":349,"_156":138,"_153":293,"_95":99,"_164":350,"_162":232,"_100":192,"_155":-5,"_105":351,"_157":352,"_166":-5},"9841effa-5a76-11f0-a19d-f69ea79377d9","# Talk Submission System\n\nA complete talk submission system with Discord integration for event organizers.\n\n## Features\n\n- **Talk Submission Form**: Collects speaker name, talk context, and submission type\n- **Discord Integration**: Automatically creates channels and sends notifications\n- **Database Storage**: Tracks all submissions with SQLite\n- **Responsive UI**: Clean, modern interface built with React and TailwindCSS\n\n## How It Works\n\n1. **Form Submission**: Users fill out the talk submission form\n2. **Database Storage**: Submission is saved to SQLite database\n3. **Discord Channel Creation**: A dedicated channel is created for the talk discussion\n4. **Organizer Notification**: A message is posted to the organizers' channel\n5. **Invite Link**: User receives a Discord invite link to join the discussion\n\n## Project Structure\n\n```\n├── backend/\n│ └── index.ts # Main API server with Hono\n├── frontend/\n│ ├── index.html # Main HTML template\n│ ├── index.tsx # React app entry point\n│ └── components/\n│ ├── App.tsx # Main app component\n│ ├── TalkSubmissionForm.tsx # Form component\n│ └── SubmissionSuccess.tsx # Success page component\n├── shared/\n│ └── types.ts # Shared TypeScript types\n└── README.md\n```\n\n## Setup\n\n### Environment Variables\n\nYou'll need to set up the following environment variables for Discord integration:\n\n- `DISCORD_BOT_TOKEN`: Your Discord bot token\n- `DISCORD_GUILD_ID`: Your Discord server ID\n- `DISCORD_ORGANIZERS_CHANNEL_ID`: Channel ID where organizer notifications are sent\n- `DISCORD_CATEGORY_ID` (optional): Category ID for organizing talk channels\n- `DISCORD_TEST_CATEGORY_ID` (optional): Category ID for organizing test channels\n- `DISCORD_TEST_ORGANIZERS_CHANNEL_ID` (optional): Channel ID for test announcements\n\n#### Testing Environment Variables\n\nThe following environment variables are used for testing the Discord integration without affecting production channels:\n\n- `ENABLE_TEST_API`: Set to \"true\" to enable the test API endpoint (required for testing)\n- `DISCORD_TEST_CATEGORY_ID`: Separate category for test channels to keep them organized\n- `DISCORD_TEST_ORGANIZERS_CHANNEL_ID`: Separate channel for test notifications to avoid spamming production organizers\n\n**Testing the Discord Integration:**\n\n```bash\ncurl -X POST https://rustnyc-talks.val.run/api/discord/test \\\n -H \"Content-Type: application/json\" \\\n -d '{\"channelName\": \"my-test-channel\", \"firstMessage\": \"Hello from test endpoint!\"}'\n```\n\n**Parameters:**\n- `channelName` (required): Name for the test channel (will be sanitized for Discord)\n- `firstMessage` (required): First message to send to the channel\n\nThis will create a test channel with the specified name, send the first message, and return an invite link. If test environment variables are configured, it will also notify the test organizers channel.\n\n### Discord Bot Setup\n\n1. Create a Discord application at https://discord.com/developers/applications\n2. Create a bot and copy the token\n3. Invite the bot to your server with the following permissions:\n - Manage Channels\n - Send Messages\n - Create Instant Invite\n - View Channels\n\n### Database\n\nThe system uses SQLite with the following schema:\n\n```sql\nCREATE TABLE talk_submissions_1 (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n speaker_name TEXT NOT NULL,\n talk_context TEXT NOT NULL,\n is_on_behalf BOOLEAN NOT NULL,\n discord_channel_id TEXT,\n discord_invite_link TEXT,\n created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n);\n```\n\n## API Endpoints\n\n- `POST /api/submissions` - Submit a new talk proposal\n- `GET /api/submissions` - Get all submissions (admin)\n- `POST /api/discord/test` - Test Discord integration (creates test channel and sends message)\n\n## Discord Integration Status\n\n✅ **Discord integration is fully implemented with comprehensive logging**\n\nThe system will automatically:\n- Create Discord channels for each talk submission\n- Generate invite links for the channels \n- Post notifications to the organizers channel\n\n**Comprehensive Logging**: The system includes detailed logging throughout the Discord integration process:\n- 🔍 Environment variable checks on startup\n- 🎯 API request tracking with submission details\n- 🔧 Discord channel creation with API responses\n- 🔗 Invite link generation with full details\n- 📢 Organizer notifications with message content\n- 💥 Detailed error logging with stack traces and specific Discord error codes\n- 📊 Final result summaries\n\n**Fallback behavior**: If Discord credentials are not provided, the system will use placeholder values and log what would have been done, allowing the form to still function for testing.\n\n**Debugging**: Use the requests tool to view detailed logs of each submission, including all Discord API interactions and any errors that occur.\n\n## Usage\n\n1. Fill out the talk submission form\n2. Submit the form\n3. Receive a Discord invite link\n4. Join the Discord channel to discuss your talk with organizers\n\n## Tech Stack\n\n- **Backend**: Hono (API framework)\n- **Frontend**: React 18.2.0 with TypeScript\n- **Database**: SQLite\n- **Styling**: TailwindCSS\n- **Platform**: Val Town (Deno runtime)",["D",1751812585510],48,{"_103":354,"_156":138,"_153":293,"_95":99,"_164":355,"_162":232,"_100":212,"_155":-5,"_105":356,"_157":357,"_166":-5},"81d3700a-5a75-11f0-8d00-f69ea79377d9","# Talk Submission System\n\nA complete talk submission system with Discord integration for event organizers.\n\n## Features\n\n- **Talk Submission Form**: Collects speaker name, talk context, and submission type\n- **Discord Integration**: Automatically creates channels and sends notifications\n- **Database Storage**: Tracks all submissions with SQLite\n- **Responsive UI**: Clean, modern interface built with React and TailwindCSS\n\n## How It Works\n\n1. **Form Submission**: Users fill out the talk submission form\n2. **Database Storage**: Submission is saved to SQLite database\n3. **Discord Channel Creation**: A dedicated channel is created for the talk discussion\n4. **Organizer Notification**: A message is posted to the organizers' channel\n5. **Invite Link**: User receives a Discord invite link to join the discussion\n\n## Project Structure\n\n```\n├── backend/\n│ └── index.ts # Main API server with Hono\n├── frontend/\n│ ├── index.html # Main HTML template\n│ ├── index.tsx # React app entry point\n│ └── components/\n│ ├── App.tsx # Main app component\n│ ├── TalkSubmissionForm.tsx # Form component\n│ └── SubmissionSuccess.tsx # Success page component\n├── shared/\n│ └── types.ts # Shared TypeScript types\n└── README.md\n```\n\n## Setup\n\n### Environment Variables\n\nYou'll need to set up the following environment variables for Discord integration:\n\n- `DISCORD_BOT_TOKEN`: Your Discord bot token\n- `DISCORD_GUILD_ID`: Your Discord server ID\n- `DISCORD_ORGANIZERS_CHANNEL_ID`: Channel ID where organizer notifications are sent\n- `DISCORD_CATEGORY_ID` (optional): Category ID for organizing talk channels\n- `DISCORD_TEST_CATEGORY_ID` (optional): Category ID for organizing test channels\n- `DISCORD_TEST_ORGANIZERS_CHANNEL_ID` (optional): Channel ID for test announcements\n\n#### Testing Environment Variables\n\nThe following environment variables are used for testing the Discord integration without affecting production channels:\n\n- `DISCORD_TEST_CATEGORY_ID`: Separate category for test channels to keep them organized\n- `DISCORD_TEST_ORGANIZERS_CHANNEL_ID`: Separate channel for test notifications to avoid spamming production organizers\n\n**Testing the Discord Integration:**\n\n```bash\ncurl -X POST http://localhost:8000/api/discord/test \\\n -H \"Content-Type: application/json\" \\\n -d '{\"channelName\": \"my-test-channel\", \"firstMessage\": \"Hello from test endpoint!\"}'\n```\n\n**Parameters:**\n- `channelName` (required): Name for the test channel (will be sanitized for Discord)\n- `firstMessage` (required): First message to send to the channel\n\nThis will create a test channel with the specified name, send the first message, and return an invite link. If test environment variables are configured, it will also notify the test organizers channel.\n\n### Discord Bot Setup\n\n1. Create a Discord application at https://discord.com/developers/applications\n2. Create a bot and copy the token\n3. Invite the bot to your server with the following permissions:\n - Manage Channels\n - Send Messages\n - Create Instant Invite\n - View Channels\n\n### Database\n\nThe system uses SQLite with the following schema:\n\n```sql\nCREATE TABLE talk_submissions_1 (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n speaker_name TEXT NOT NULL,\n talk_context TEXT NOT NULL,\n is_on_behalf BOOLEAN NOT NULL,\n discord_channel_id TEXT,\n discord_invite_link TEXT,\n created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n);\n```\n\n## API Endpoints\n\n- `POST /api/submissions` - Submit a new talk proposal\n- `GET /api/submissions` - Get all submissions (admin)\n- `POST /api/discord/test` - Test Discord integration (creates test channel and sends message)\n\n## Discord Integration Status\n\n✅ **Discord integration is fully implemented with comprehensive logging**\n\nThe system will automatically:\n- Create Discord channels for each talk submission\n- Generate invite links for the channels \n- Post notifications to the organizers channel\n\n**Comprehensive Logging**: The system includes detailed logging throughout the Discord integration process:\n- 🔍 Environment variable checks on startup\n- 🎯 API request tracking with submission details\n- 🔧 Discord channel creation with API responses\n- 🔗 Invite link generation with full details\n- 📢 Organizer notifications with message content\n- 💥 Detailed error logging with stack traces and specific Discord error codes\n- 📊 Final result summaries\n\n**Fallback behavior**: If Discord credentials are not provided, the system will use placeholder values and log what would have been done, allowing the form to still function for testing.\n\n**Debugging**: Use the requests tool to view detailed logs of each submission, including all Discord API interactions and any errors that occur.\n\n## Usage\n\n1. Fill out the talk submission form\n2. Submit the form\n3. Receive a Discord invite link\n4. Join the Discord channel to discuss your talk with organizers\n\n## Tech Stack\n\n- **Backend**: Hono (API framework)\n- **Frontend**: React 18.2.0 with TypeScript\n- **Database**: SQLite\n- **Styling**: TailwindCSS\n- **Platform**: Val Town (Deno runtime)",["D",1751812118419],45,{"_103":359,"_156":138,"_153":293,"_95":99,"_164":360,"_162":232,"_100":185,"_155":-5,"_105":361,"_157":362,"_166":-5},"3d1f1faa-5a74-11f0-8d81-f69ea79377d9","# Talk Submission System\n\nA complete talk submission system with Discord integration for event organizers.\n\n## Features\n\n- **Talk Submission Form**: Collects speaker name, talk context, and submission type\n- **Discord Integration**: Automatically creates channels and sends notifications\n- **Database Storage**: Tracks all submissions with SQLite\n- **Responsive UI**: Clean, modern interface built with React and TailwindCSS\n\n## How It Works\n\n1. **Form Submission**: Users fill out the talk submission form\n2. **Database Storage**: Submission is saved to SQLite database\n3. **Discord Channel Creation**: A dedicated channel is created for the talk discussion\n4. **Organizer Notification**: A message is posted to the organizers' channel\n5. **Invite Link**: User receives a Discord invite link to join the discussion\n\n## Project Structure\n\n```\n├── backend/\n│ └── index.ts # Main API server with Hono\n├── frontend/\n│ ├── index.html # Main HTML template\n│ ├── index.tsx # React app entry point\n│ └── components/\n│ ├── App.tsx # Main app component\n│ ├── TalkSubmissionForm.tsx # Form component\n│ └── SubmissionSuccess.tsx # Success page component\n├── shared/\n│ └── types.ts # Shared TypeScript types\n└── README.md\n```\n\n## Setup\n\n### Environment Variables\n\nYou'll need to set up the following environment variables for Discord integration:\n\n- `DISCORD_BOT_TOKEN`: Your Discord bot token\n- `DISCORD_GUILD_ID`: Your Discord server ID\n- `DISCORD_ORGANIZERS_CHANNEL_ID`: Channel ID where organizer notifications are sent\n- `DISCORD_CATEGORY_ID` (optional): Category ID for organizing talk channels\n- `DISCORD_TEST_CATEGORY_ID` (optional): Category ID for organizing test channels\n\n### Discord Bot Setup\n\n1. Create a Discord application at https://discord.com/developers/applications\n2. Create a bot and copy the token\n3. Invite the bot to your server with the following permissions:\n - Manage Channels\n - Send Messages\n - Create Instant Invite\n - View Channels\n\n### Database\n\nThe system uses SQLite with the following schema:\n\n```sql\nCREATE TABLE talk_submissions_1 (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n speaker_name TEXT NOT NULL,\n talk_context TEXT NOT NULL,\n is_on_behalf BOOLEAN NOT NULL,\n discord_channel_id TEXT,\n discord_invite_link TEXT,\n created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n);\n```\n\n## API Endpoints\n\n- `POST /api/submissions` - Submit a new talk proposal\n- `GET /api/submissions` - Get all submissions (admin)\n- `POST /api/discord/test` - Test Discord integration (creates test channel and sends message)\n\n## Discord Integration Status\n\n✅ **Discord integration is fully implemented with comprehensive logging**\n\nThe system will automatically:\n- Create Discord channels for each talk submission\n- Generate invite links for the channels \n- Post notifications to the organizers channel\n\n**Comprehensive Logging**: The system includes detailed logging throughout the Discord integration process:\n- 🔍 Environment variable checks on startup\n- 🎯 API request tracking with submission details\n- 🔧 Discord channel creation with API responses\n- 🔗 Invite link generation with full details\n- 📢 Organizer notifications with message content\n- 💥 Detailed error logging with stack traces and specific Discord error codes\n- 📊 Final result summaries\n\n**Fallback behavior**: If Discord credentials are not provided, the system will use placeholder values and log what would have been done, allowing the form to still function for testing.\n\n**Debugging**: Use the requests tool to view detailed logs of each submission, including all Discord API interactions and any errors that occur.\n\n## Usage\n\n1. Fill out the talk submission form\n2. Submit the form\n3. Receive a Discord invite link\n4. Join the Discord channel to discuss your talk with organizers\n\n### Testing Discord Integration\n\nTo test the Discord integration:\n\n```bash\ncurl -X POST http://localhost:8000/api/discord/test \\\n -H \"Content-Type: application/json\" \\\n -d '{\"channelName\": \"my-test-channel\", \"firstMessage\": \"Hello from test endpoint!\"}'\n```\n\nThis will create a test channel with the specified name, send the first message, and return an invite link.\n\n**Parameters:**\n- `channelName` (required): Name for the test channel (will be sanitized for Discord)\n- `firstMessage` (required): First message to send to the channel\n\n## Tech Stack\n\n- **Backend**: Hono (API framework)\n- **Frontend**: React 18.2.0 with TypeScript\n- **Database**: SQLite\n- **Styling**: TailwindCSS\n- **Platform**: Val Town (Deno runtime)",["D",1751811573648],43,{"_103":364,"_156":138,"_153":293,"_95":99,"_164":365,"_162":232,"_100":158,"_155":-5,"_105":366,"_157":367,"_166":-5},"9cbf3762-5108-11f0-adde-f69ea79377d9","# Talk Submission System\n\nA complete talk submission system with Discord integration for event organizers.\n\n## Features\n\n- **Talk Submission Form**: Collects speaker name, talk context, and submission type\n- **Discord Integration**: Automatically creates channels and sends notifications\n- **Database Storage**: Tracks all submissions with SQLite\n- **Responsive UI**: Clean, modern interface built with React and TailwindCSS\n\n## How It Works\n\n1. **Form Submission**: Users fill out the talk submission form\n2. **Database Storage**: Submission is saved to SQLite database\n3. **Discord Channel Creation**: A dedicated channel is created for the talk discussion\n4. **Organizer Notification**: A message is posted to the organizers' channel\n5. **Invite Link**: User receives a Discord invite link to join the discussion\n\n## Project Structure\n\n```\n├── backend/\n│ └── index.ts # Main API server with Hono\n├── frontend/\n│ ├── index.html # Main HTML template\n│ ├── index.tsx # React app entry point\n│ └── components/\n│ ├── App.tsx # Main app component\n│ ├── TalkSubmissionForm.tsx # Form component\n│ └── SubmissionSuccess.tsx # Success page component\n├── shared/\n│ └── types.ts # Shared TypeScript types\n└── README.md\n```\n\n## Setup\n\n### Environment Variables\n\nYou'll need to set up the following environment variables for Discord integration:\n\n- `DISCORD_BOT_TOKEN`: Your Discord bot token\n- `DISCORD_GUILD_ID`: Your Discord server ID\n- `DISCORD_ORGANIZERS_CHANNEL_ID`: Channel ID where organizer notifications are sent\n- `DISCORD_CATEGORY_ID` (optional): Category ID for organizing talk channels\n\n### Discord Bot Setup\n\n1. Create a Discord application at https://discord.com/developers/applications\n2. Create a bot and copy the token\n3. Invite the bot to your server with the following permissions:\n - Manage Channels\n - Send Messages\n - Create Instant Invite\n - View Channels\n\n### Database\n\nThe system uses SQLite with the following schema:\n\n```sql\nCREATE TABLE talk_submissions_1 (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n speaker_name TEXT NOT NULL,\n talk_context TEXT NOT NULL,\n is_on_behalf BOOLEAN NOT NULL,\n discord_channel_id TEXT,\n discord_invite_link TEXT,\n created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n);\n```\n\n## API Endpoints\n\n- `POST /api/submissions` - Submit a new talk proposal\n- `GET /api/submissions` - Get all submissions (admin)\n\n## Discord Integration Status\n\n✅ **Discord integration is fully implemented with comprehensive logging**\n\nThe system will automatically:\n- Create Discord channels for each talk submission\n- Generate invite links for the channels \n- Post notifications to the organizers channel\n\n**Comprehensive Logging**: The system includes detailed logging throughout the Discord integration process:\n- 🔍 Environment variable checks on startup\n- 🎯 API request tracking with submission details\n- 🔧 Discord channel creation with API responses\n- 🔗 Invite link generation with full details\n- 📢 Organizer notifications with message content\n- 💥 Detailed error logging with stack traces and specific Discord error codes\n- 📊 Final result summaries\n\n**Fallback behavior**: If Discord credentials are not provided, the system will use placeholder values and log what would have been done, allowing the form to still function for testing.\n\n**Debugging**: Use the requests tool to view detailed logs of each submission, including all Discord API interactions and any errors that occur.\n\n## Usage\n\n1. Fill out the talk submission form\n2. Submit the form\n3. Receive a Discord invite link\n4. Join the Discord channel to discuss your talk with organizers\n\n## Tech Stack\n\n- **Backend**: Hono (API framework)\n- **Frontend**: React 18.2.0 with TypeScript\n- **Database**: SQLite\n- **Styling**: TailwindCSS\n- **Platform**: Val Town (Deno runtime)",["D",1750775787973],22,{"_103":369,"_156":138,"_153":293,"_95":99,"_164":370,"_162":232,"_100":278,"_155":-5,"_105":371,"_157":372,"_166":-5},"e38ef9bc-5107-11f0-a8fa-f69ea79377d9","# Talk Submission System\n\nA complete talk submission system with Discord integration for event organizers.\n\n## Features\n\n- **Talk Submission Form**: Collects speaker name, talk context, and submission type\n- **Discord Integration**: Automatically creates channels and sends notifications\n- **Database Storage**: Tracks all submissions with SQLite\n- **Responsive UI**: Clean, modern interface built with React and TailwindCSS\n\n## How It Works\n\n1. **Form Submission**: Users fill out the talk submission form\n2. **Database Storage**: Submission is saved to SQLite database\n3. **Discord Channel Creation**: A dedicated channel is created for the talk discussion\n4. **Organizer Notification**: A message is posted to the organizers' channel\n5. **Invite Link**: User receives a Discord invite link to join the discussion\n\n## Project Structure\n\n```\n├── backend/\n│ └── index.ts # Main API server with Hono\n├── frontend/\n│ ├── index.html # Main HTML template\n│ ├── index.tsx # React app entry point\n│ └── components/\n│ ├── App.tsx # Main app component\n│ ├── TalkSubmissionForm.tsx # Form component\n│ └── SubmissionSuccess.tsx # Success page component\n├── shared/\n│ └── types.ts # Shared TypeScript types\n└── README.md\n```\n\n## Setup\n\n### Environment Variables\n\nYou'll need to set up the following environment variables for Discord integration:\n\n- `DISCORD_BOT_TOKEN`: Your Discord bot token\n- `DISCORD_GUILD_ID`: Your Discord server ID\n- `DISCORD_ORGANIZERS_CHANNEL_ID`: Channel ID where organizer notifications are sent\n- `DISCORD_CATEGORY_ID` (optional): Category ID for organizing talk channels\n\n### Discord Bot Setup\n\n1. Create a Discord application at https://discord.com/developers/applications\n2. Create a bot and copy the token\n3. Invite the bot to your server with the following permissions:\n - Manage Channels\n - Send Messages\n - Create Instant Invite\n - View Channels\n\n### Database\n\nThe system uses SQLite with the following schema:\n\n```sql\nCREATE TABLE talk_submissions_1 (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n speaker_name TEXT NOT NULL,\n talk_context TEXT NOT NULL,\n is_on_behalf BOOLEAN NOT NULL,\n discord_channel_id TEXT,\n discord_invite_link TEXT,\n created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n);\n```\n\n## API Endpoints\n\n- `POST /api/submissions` - Submit a new talk proposal\n- `GET /api/submissions` - Get all submissions (admin)\n\n## Discord Integration Status\n\n✅ **Discord integration is fully implemented**\n\nThe system will automatically:\n- Create Discord channels for each talk submission\n- Generate invite links for the channels \n- Post notifications to the organizers channel\n\n**Fallback behavior**: If Discord credentials are not provided, the system will use placeholder values and log what would have been done, allowing the form to still function for testing.\n\n## Usage\n\n1. Fill out the talk submission form\n2. Submit the form\n3. Receive a Discord invite link\n4. Join the Discord channel to discuss your talk with organizers\n\n## Tech Stack\n\n- **Backend**: Hono (API framework)\n- **Frontend**: React 18.2.0 with TypeScript\n- **Database**: SQLite\n- **Styling**: TailwindCSS\n- **Platform**: Val Town (Deno runtime)",["D",1750775477279],13,{"_103":374,"_156":138,"_153":293,"_95":99,"_164":375,"_162":232,"_100":32,"_155":-5,"_105":376,"_157":377,"_166":-5},"bfef9c0a-5107-11f0-b497-f69ea79377d9","# Talk Submission System\n\nA complete talk submission system with Discord integration for event organizers.\n\n## Features\n\n- **Talk Submission Form**: Collects speaker name, talk context, and submission type\n- **Discord Integration**: Automatically creates channels and sends notifications\n- **Database Storage**: Tracks all submissions with SQLite\n- **Responsive UI**: Clean, modern interface built with React and TailwindCSS\n\n## How It Works\n\n1. **Form Submission**: Users fill out the talk submission form\n2. **Database Storage**: Submission is saved to SQLite database\n3. **Discord Channel Creation**: A dedicated channel is created for the talk discussion\n4. **Organizer Notification**: A message is posted to the organizers' channel\n5. **Invite Link**: User receives a Discord invite link to join the discussion\n\n## Project Structure\n\n```\n├── backend/\n│ └── index.ts # Main API server with Hono\n├── frontend/\n│ ├── index.html # Main HTML template\n│ ├── index.tsx # React app entry point\n│ └── components/\n│ ├── App.tsx # Main app component\n│ ├── TalkSubmissionForm.tsx # Form component\n│ └── SubmissionSuccess.tsx # Success page component\n├── shared/\n│ └── types.ts # Shared TypeScript types\n└── README.md\n```\n\n## Setup\n\n### Environment Variables\n\nYou'll need to set up the following environment variables for Discord integration:\n\n- `DISCORD_BOT_TOKEN`: Your Discord bot token\n- `DISCORD_GUILD_ID`: Your Discord server ID\n- `DISCORD_ORGANIZERS_CHANNEL_ID`: Channel ID where organizer notifications are sent\n- `DISCORD_CATEGORY_ID` (optional): Category ID for organizing talk channels\n\n### Discord Bot Setup\n\n1. Create a Discord application at https://discord.com/developers/applications\n2. Create a bot and copy the token\n3. Invite the bot to your server with the following permissions:\n - Manage Channels\n - Send Messages\n - Create Instant Invite\n - View Channels\n\n### Database\n\nThe system uses SQLite with the following schema:\n\n```sql\nCREATE TABLE talk_submissions_1 (\n id INTEGER PRIMARY KEY AUTOINCREMENT,\n speaker_name TEXT NOT NULL,\n talk_context TEXT NOT NULL,\n is_on_behalf BOOLEAN NOT NULL,\n discord_channel_id TEXT,\n discord_invite_link TEXT,\n created_at DATETIME DEFAULT CURRENT_TIMESTAMP\n);\n```\n\n## API Endpoints\n\n- `POST /api/submissions` - Submit a new talk proposal\n- `GET /api/submissions` - Get all submissions (admin)\n\n## Discord Integration Status\n\n⚠️ **Discord integration is currently using placeholder implementations**\n\nThe following functions need to be implemented with actual Discord API calls:\n\n- `createDiscordChannel()` - Create a new channel for the talk\n- `createDiscordInvite()` - Generate an invite link for the channel\n- `postToOrganizersChannel()` - Post notification to organizers\n\nOnce you provide the Discord bot credentials, these will be fully implemented.\n\n## Usage\n\n1. Fill out the talk submission form\n2. Submit the form\n3. Receive a Discord invite link\n4. Join the Discord channel to discuss your talk with organizers\n\n## Tech Stack\n\n- **Backend**: Hono (API framework)\n- **Frontend**: React 18.2.0 with TypeScript\n- **Database**: SQLite\n- **Styling**: TailwindCSS\n- **Platform**: Val Town (Deno runtime)",["D",1750775417519],10,"versions",[380,382,383,384,385,386,387],{"_232":346,"_381":348},"previous",{"_232":348,"_381":353},{"_232":353,"_381":358},{"_232":358,"_381":363},{"_232":363,"_381":368},{"_232":368,"_381":373},{"_232":373,"_381":-5},"versionNumber","page","hasNext","actionData","errors"]

History for README.md