How canvasbird/canvasboard works
Project type and purpose
• Canvasboard is a single‑page web application (SPA) built with Angular (frontend), which communicates via REST APIs with a FastAPI backend (hosted separately). It provides an interactive “canvas” workspace with pluggable tools for teaching, presenting, and collaboration.
• The README confirms that backend (FastAPI + MongoDB) and cloud hosting (AWS) are separate concerns; this repository holds the frontend only.
File structure
• Top‑level config: Dockerfile, GitHub workflows, lint/prettier, Angular CLI config (angular.json).
• src/app: Angular modules and lazy‑loaded feature modules organized under components, plugins, services, shared.
• components/… each feature has its own routing.module.ts and module.ts
• plugins/… custom plugin modules and CLI loader (src/app/plugins_cli.js)
• services/: AuthService, RestService, LoadingService
• shared/: route guards, pipes
• src/environments: environment.ts & production
• e2e/: end‑to‑end tests with Protractor
• Interfaces define type contracts for plugin parameters, board data, dashboard, etc.
README for additional insights
• Mentions dependencies: Angular, Bootstrap, jQuery, FastAPI, MongoDB, AWS.
• States that Canvasboard is standalone and extensible via plugins.
• Indicates separate backend repo handling persistence and authentication.
Detailing and capturing essential architecture
• Do not simply dump every file; group by module or concern (UI, services, plugins).
• Environment configurations feeding into the build pipeline (Angular CLI → Docker → Netlify).
• Authentication flow with guard symbols protecting feature routes.