38 lines
2.0 KiB
Markdown
38 lines
2.0 KiB
Markdown
## Why
|
|
|
|
Users need a quick, concise view of fetched news without reading long article text. Adding a TL;DR summary flow improves scan speed, reading experience, and engagement while keeping source transparency.
|
|
|
|
## What Changes
|
|
|
|
- **New Capabilities:**
|
|
- Generate concise article summaries via Perplexity when news is fetched.
|
|
- Store structured summary content in the database using the required display template.
|
|
- Fetch and attach an appropriate royalty-free image for each summarized article.
|
|
- Render summary content in a modal dialog from the landing page.
|
|
- Add Umami event tagging for modal opens, closes, and source link-outs.
|
|
- **Backend:**
|
|
- Extend ingestion to call Perplexity summary generation and persist summary output.
|
|
- Integrate royalty-free image sourcing (prefer MCP path when available).
|
|
- **Frontend:**
|
|
- Add summary modal UI and interaction flow.
|
|
- Add event tracking for all required user actions in the modal.
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
- `article-tldr-summary`: Generate and persist concise TL;DR + summary content per fetched article using Perplexity.
|
|
- `summary-modal-experience`: Display summary content in a modal dialog using the standardized template format.
|
|
- `royalty-free-image-enrichment`: Attach appropriate royalty-free images for summarized articles, leveraging MCP integration when available.
|
|
- `summary-analytics-tagging`: Track summary modal opens, closes, and external source link-outs via Umami event tags.
|
|
|
|
### Modified Capabilities
|
|
- None.
|
|
|
|
## Impact
|
|
|
|
- **Code:** Ingestion pipeline, storage model/schema, API response payloads, and frontend modal interactions will be updated.
|
|
- **APIs:** Existing news payloads will include summary/template-ready fields and image metadata.
|
|
- **Dependencies:** Reuses Perplexity; may add/enable royalty-free image provider integration (including MCP route if available).
|
|
- **Infrastructure:** No major topology change expected.
|
|
- **Data:** Database will store summary artifacts and associated image/source metadata.
|