Files
social-media/docs/TASKS/release-communications/002-frontend-whats-new.md
Jonathan Bourdon b6eb348605
All checks were successful
deploy-socialize / image (push) Successful in 1m12s
deploy-socialize / deploy (push) Successful in 19s
feat: add release communications
2026-05-07 21:04:29 -04:00

1.7 KiB
Raw Blame History

Task: Frontend Whats New experience

Goal

Add the user-facing Whats New experience for published release updates and unread state.

Feature Spec

  • docs/FEATURES/release-communications.md

Scope

  • Add feature-owned frontend code under frontend/src/features/release-communications/.
  • Add /app/updates.
  • Add an app shell entry or badge for unread release updates.
  • Fetch visible published release updates from the backend.
  • Show unread state for update entries.
  • Mark an update as read when opened.
  • Add a mark-all-read action.
  • Optionally show a non-blocking login-time Whats New panel when unread updates exist.
  • Add English and French locale strings.
  • Keep developer authoring UI, commit reconciliation, and email digest out of this task.

Likely Files

  • frontend/src/router/router.js
  • frontend/src/layouts/main/**
  • frontend/src/features/release-communications/**
  • frontend/src/locales/en.json
  • frontend/src/locales/fr.json

Notes

  • The user-facing update feed must be curated and should not show raw commit SHAs, commit subjects, branch names, or internal-only work.
  • Keep the UI compact and app-like. This is an operational app surface, not a marketing release notes page.
  • Use the shared Axios API client in frontend/src/plugins/api.js.

Validation

cd frontend
npm run build

Done When

  • Authenticated users can open /app/updates.
  • The app shell shows unread update count.
  • Published visible updates are listed newest first.
  • Unread updates are visually distinct.
  • Opening an update marks it read.
  • Users can mark all visible updates read.
  • UI strings exist in English and French.
  • Frontend build passes.