How seakyy/eventfeedbackapp works
Project type and purpose
• This is a full-stack, web-based feedback platform built with ASP.NET Core Razor Pages.
• Purpose: Allow admins to create “sessions” and questions (CRUD), let participants join via QR or session ID, submit responses in real time, and let admins view live charts (via Chart.js) updated over SignalR.
File structure
• Frontend (Razor Pages UI):
• src/Pages/Admin – admin workflows (CreateSession, CreateQuestion, Results, etc.)
• src/Pages/Feedback – participant workflows (JoinSession, Questions)
• src/Pages/Shared – layout and partial views (_Layout, validation scripts)
• wwwroot – static assets (css, js, Bootstrap, jQuery)
• Backend services & API:
• Program.cs & Startup pipeline (middleware, routing)
• src/Middleware/AdminAuthMiddleware.cs – custom auth guard for admin endpoints
• src/Hubs/FeedbackHub.cs – SignalR hub for push updates
• Data layer:
• src/Data/AppDbContext.cs – EF Core DbContext
• src/Models/*.cs – domain entities (Session, Question, Option, Response)
• src/Migrations – EF migrations for schema
• feedback.db – SQLite database file
• Configuration & build:
• appsettings.json / appsettings.Development.json
• launchSettings.json
• .csproj/.sln files
README for additional insights
• Core features: dynamic question engine, mobile-first UX (QR code), real-time dashboard.
• Endpoints of interest: /Admin/CreateSession, /Feedback/JoinSession, /Feedback/Questions/{id}, /Admin/Results/{id}.
Detailed breakdown to capture all architectural elements
• Middleware (AdminAuth)
• Page Handlers (Admin vs. Feedback folders)
• Hubs (FeedbackHub)
• Data (AppDbContext + Migrations + Models)
• Two feedback modes: polling vs. SignalR (admin can choose either ResultsPolling or ResultsSignalR).
• Asset pipeline: Browser ← static files (wwwroot)