admin/40227-vm
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
40227-vm/frontend/docs/communications-integration.md
Dmitri d4a5378adf Refactor: migrate frontend to Vite/React, add product backend modules 
Frontend:
- Replace Next.js with Vite + React + TypeScript
- Add new component architecture (app-shell, sidebar, dashboard modules)
- Implement product modules: FRAME, safety protocols, walkthrough checkin,
  campus/staff attendance, personality quiz, sign language, classroom timer
- Add shadcn/ui component library with Tailwind CSS
- Remove legacy generated components, stores, and pages

Backend:
- Add product migrations: frame_entries, user_progress, safety_quiz_results,
  walkthrough_checkins, communication_events, personality_quiz_results,
  campus_attendance_config/summaries, staff_attendance_records, content_catalog
- Add corresponding models, services, and routes
- Implement cookie-based auth with refresh token rotation
- Add content catalog seeder with product content
- Migrate to ESLint flat config
- Switch from yarn to npm

Infrastructure:
- Update .gitignore for new tooling
- Add project documentation (CLAUDE.md, docs/)
- Remove deprecated config files and yarn.lock

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-06-09 15:18:23 +02:00

1.9 KiB
Raw Blame History

Communications Frontend Integration

Purpose

Parent communication, internal alerts, and dashboard upcoming events follow the frontend three-layer architecture.

View -> Business Logic -> API/Data Access -> Backend

Files

View layer:

  • frontend/src/components/parent-communication/ParentCommunicationModule.tsx
  • frontend/src/components/internal-alerts/InternalAlertsModule.tsx
  • frontend/src/components/safety-protocols/SafetyProtocolsModule.tsx
  • frontend/src/components/frameworks/MoreModules.tsx as a module export hub
  • frontend/src/components/frameworks/Dashboard.tsx
  • frontend/src/components/dashboard/DashboardUpcomingEvents.tsx

Business logic layer:

  • frontend/src/business/communications/hooks.ts
  • frontend/src/business/communications/selectors.ts
  • frontend/src/business/dashboard/hooks.ts

API/data access layer:

  • frontend/src/shared/api/communications.ts
  • frontend/src/shared/types/communications.ts
  • frontend/src/shared/constants/communications.ts

Behavior

  • Parent message logs load from GET /api/communications/parent-messages.
  • Parent messages save through POST /api/communications/parent-messages.
  • Internal alerts load from GET /api/communications/events.
  • Director/superintendent users create alerts through POST /api/communications/events.
  • Dashboard upcoming events read the same backend event data as the internal alerts module through useDashboardPage.
  • Safety protocols are loaded through the content catalog backend contract and rendered in a focused view module.
  • Approved parent templates and event display constants live in shared constants.
  • Parent communication, internal alerts, and safety protocols use shared UI primitives for buttons, form controls, and status panels.

Remaining Related Work

Alert acknowledgments are still local UI state. Add a backend acknowledgment table when acknowledgments must survive reloads or feed compliance reporting.