How berkmancenter/frankly works
Project type and purpose
• Frankly is a full-stack, web-based deliberations platform
• Client: Flutter web application (client/)
• Backend: Firebase services (Firestore, Auth, Hosting), Cloud Functions (Dart), plus a standalone “matching” microservice
• Shared models: data_models/ library used by both client and functions
• External integrations: Agora for video chat, Mux for livestream, Stripe for payments, Typeform, calendar feeds
File structure
• Top-level directories:
– client/: Flutter code (core/data/services, features/, presentation/views, utils, widgets)
– firebase/firestore/: Firestore rules & indexes
– firebase/functions/: Cloud Functions in Dart, organized by domain (community, events, live_meetings, templates, utils, infra)
– matching/: separate microservice (Dart/Node) for participant-to-breakout matching
– data_models/: shared Dart data classes (admin, events, chat, community, etc.)
– e2e/: Playwright test fixtures and page-object tests
– docs/: MkDocs site content
• Patterns spotted:
– Layered frontend (data providers → services → presenters → UI)
– Domain-based Cloud Functions, triggered by Firestore writes or HTTP/HTTPS calls
– Shared schemas in data_models/
Extract architecture hints from README
• Purpose: host video-enabled conversations, match participants into breakout rooms, structured event templates
• AGPL-licensed, external dependencies chosen accordingly
• Encourages reading the online docs for high-level overviews