How anguscow0508/submission_system works
This is a small FastAPI article-submission and editorial-review application. Authors create and edit drafts, submit them for review, and editors inspect the queue before approving or returning submissions; the article status records these stages. The main routes also serve page templates and static assets, while a connection helper opens PostgreSQL sessions. Route behavior and database access are visible in main.py and db.py; the README is empty, and schema.sql and templates were not sampled, so their internals are not inferred.
Main entry points: main.py FastAPI routes · schema.sql Article store · db.py DB connection · templates Page templates
Components 12
Web application
- FastAPI routes
main.py - Page templates
templates - Static assets
static
Submission workflow
- Author drafts
main.py - Submission status
main.py - Editorial queue
main.py - Review decision
main.py
Persistence
- DB connection
db.py - Article store
database/schema.sql
Other components
- Author
- Editor
- PostgreSQL
Connections 14
- Author → FastAPI routes: uses
main.py - Editor → FastAPI routes: uses
main.py - FastAPI routes → Page templates: renders
main.py - FastAPI routes → Static assets: mounts
main.py - FastAPI routes → Author drafts: routes
main.py - FastAPI routes → Submission status: routes
main.py - FastAPI routes → Editorial queue: routes
main.py - FastAPI routes → Review decision: routes
main.py - FastAPI routes → DB connection: opens sessions
main.py - Author drafts → Article store: reads and writes
main.py - Submission status → Article store: updates status
main.py - Editorial queue → Article store: queries
main.py - Review decision → Article store: updates status
main.py - DB connection → PostgreSQL: connects
db.py