Add calendar integrations and collaboration updates
Some checks failed
Backend CI/CD / build_and_deploy (push) Has been cancelled
Frontend CI/CD / build_and_deploy (push) Has been cancelled

This commit is contained in:
2026-05-05 15:25:53 -04:00
parent c49f03ec06
commit b66c10b681
82 changed files with 8420 additions and 2048 deletions

View File

@@ -0,0 +1,32 @@
# Task: Scope content editor channels to item workspace
## Feature
`docs/FEATURES/channels.md`
## Goal
Prevent content item channel placements from mixing channels across workspaces when the app is viewed in an all-workspaces scope.
## Context
Seeded content such as `Bakery loyalty carousel` should only use channels from its own workspace. The seed source assigns it to `Atlas Bakery Instagram`, but stale editor drafts or all-workspaces channel options can show unrelated Luma channels in the content detail editor.
## Scope
- Limit content detail channel options to the content item's workspace.
- Deduplicate publication target parsing and summary serialization.
- Normalize restored editor drafts so duplicate or other-workspace known channels are not kept.
## Validation
```bash
cd frontend
npm run build
```
## Acceptance Criteria
- [x] Existing content items only offer channels from their own workspace.
- [x] Duplicate publication target strings render as one placement.
- [x] Stale restored drafts do not keep known channels from other workspaces.