Welcome to Sejong Pulse’s documentation!

Sejong Pulse is a campus-first social platform with a Next.js frontend, a FastAPI backend, Supabase-backed identity and data, AI-assisted advisor flows, and supporting services for messaging, search, recommendations, billing, and media delivery.

This documentation mirrors the classic Sphinx + Read the Docs structure used in the reference site and adapts it to the architecture, routes, and operational workflows in this repository.

Contents:

• About the Project
  • Goal
  • Target Audience
  • Core Product Areas
  • Repository Layout
  • Design Direction
• Getting Started
  • Prerequisites
  • Install the Frontend
  • Install the Backend
  • Minimum Environment Variables
  • Optional Local Infrastructure
  • Database and Schema
  • Verification Commands
  • Build the Documentation Site
• How to Use
  • 1. Sign In and Create a Profile
  • 2. Explore the Pulse Feed
  • 3. Use Discovery Features
  • 4. Chat, Join Channels, and Start Calls
  • 5. Ask the Advisor
  • 6. Manage Settings and Notifications
  • 7. Operator Workflow
• Technical Overview
  • Architecture
  • Frontend
  • Backend
  • Data and State
  • Deployment Topology
  • Non-Runtime Assets
• API Reference
  • Authentication and Onboarding
  • Profiles, Discovery, and Social Graph
  • Pulse Feed and Content
  • Chat, Advisor, Channels, and Calls
  • Notifications, Settings, Privacy, and Moderation
  • Billing
  • Health and Diagnostics
  • Notes
• Configuration Guide
  • Frontend Variables
  • Core Backend Variables
  • Search, Media, and Messaging
  • Realtime and Recommendation Services
  • Billing and Email
  • Worker and Queue Controls
  • Authentication and Identity
  • Deployment Files
  • Recommended Approach
• Maintenance and Troubleshooting
  • Routine Maintenance
  • Common Issues
  • Logging and Observability
• Contribution Guidelines
  • Contribution Workflow
  • Frontend Conventions
  • Backend Conventions
  • Database and Data Changes
  • Design and Prototyping
  • Validation Checklist
  • Documentation Expectations
• FAQ
  • Can I run Sejong Pulse without every external integration configured?
  • Where does authentication actually happen?
  • Where are the database schema and migrations?
  • Where do recommendations come from?
  • What powers the advisor?
  • Are the stitched prototype folders part of the production app?
  • What is the purpose of experiments/sejong_portal_agent?
  • How do I publish the documentation?
• Release Notes
  • Documentation Baseline
  • Recommended Next Additions