Add calendar integrations and collaboration updates
This commit is contained in:
@@ -0,0 +1,46 @@
|
||||
# Task: Add content production collaboration panel
|
||||
|
||||
## Feature
|
||||
|
||||
`docs/FEATURES/production-workflow.md`
|
||||
|
||||
## Goal
|
||||
|
||||
Make the content detail page expose the existing production collaboration data that is already loaded by the frontend store: comments, content revisions, linked assets, asset revisions, and workflow activity.
|
||||
|
||||
## Scope
|
||||
|
||||
- Add a compact production collaboration panel to `ContentItemDetailView`.
|
||||
- Keep comment creation and resolution available.
|
||||
- Show content revision history with change summaries.
|
||||
- Show linked assets and their revisions.
|
||||
- Add UI for linking a Google Drive asset and adding a new asset revision.
|
||||
- Show content-scoped notification activity as a read-only production activity feed.
|
||||
|
||||
## Likely Files
|
||||
|
||||
- `frontend/src/features/content/views/ContentItemDetailView.vue`
|
||||
- `frontend/src/features/content/stores/contentItemDetailStore.js`
|
||||
|
||||
## Out Of Scope
|
||||
|
||||
- Backend schema changes.
|
||||
- Native file uploads.
|
||||
- Mention parsing.
|
||||
- Approval comment visibility rules.
|
||||
- Reworking content variant persistence.
|
||||
|
||||
## Validation
|
||||
|
||||
```bash
|
||||
cd frontend
|
||||
npm run build
|
||||
```
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [x] Comments, revisions, assets, and activity are visible from the content detail page.
|
||||
- [x] Users can post comments from the production panel.
|
||||
- [x] Users can link a Google Drive asset to a content item.
|
||||
- [x] Users can add a new revision URL/reference to an existing asset.
|
||||
- [x] Existing create/edit content and approval controls remain available.
|
||||
32
docs/TASKS/content/005-scope-content-editor-channels.md
Normal file
32
docs/TASKS/content/005-scope-content-editor-channels.md
Normal 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.
|
||||
40
docs/TASKS/content/006-content-activity-endpoint.md
Normal file
40
docs/TASKS/content/006-content-activity-endpoint.md
Normal file
@@ -0,0 +1,40 @@
|
||||
# Task: Add content activity endpoint
|
||||
|
||||
## Feature
|
||||
|
||||
`docs/FEATURES/production-workflow.md`
|
||||
|
||||
## Goal
|
||||
|
||||
Add a content-owned activity history endpoint that is separate from user-facing notifications.
|
||||
|
||||
## Scope
|
||||
|
||||
- Add persisted content activity entries.
|
||||
- Add `GET /api/content-items/{id}/activity`.
|
||||
- Log content creation, revisions, status changes, comments, linked assets, and asset revisions.
|
||||
- Include field-level metadata for content revision changes such as title, message, channels, hashtags, and publish date.
|
||||
- Persist publish date changes sent from the content editor revision flow.
|
||||
- Use the activity endpoint from the content detail production activity tab.
|
||||
|
||||
## Out Of Scope
|
||||
|
||||
- Full diff rendering UI.
|
||||
- Deleting tags or assets.
|
||||
- Notification recipient behavior changes.
|
||||
|
||||
## Validation
|
||||
|
||||
```bash
|
||||
dotnet build backend/Socialize.slnx
|
||||
cd frontend
|
||||
npm run build
|
||||
```
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [x] `GET /api/content-items/{id}/activity` returns content history for users who can review the content item.
|
||||
- [x] Activity entries are not filtered by notification recipients.
|
||||
- [x] Content revision activity records changed fields.
|
||||
- [x] Publish date changes are saved and included in content activity.
|
||||
- [x] The content detail activity tab reads from content activity instead of notifications.
|
||||
Reference in New Issue
Block a user