docs: add implementation plan for RSS/Atom article feed support#91
docs: add implementation plan for RSS/Atom article feed support#91allenhutchison wants to merge 1 commit intomainfrom
Conversation
Comprehensive plan for adding article feed support as a new content type alongside podcasts. Covers database changes, feed detection, article fetching, pipeline integration, search, email digests, and web UI. https://claude.ai/code/session_01Yaeio8uaqmLiJnuhwHV1GY
WalkthroughThis pull request introduces a comprehensive planning document for implementing RSS/Atom article feed support as a first-class content type alongside existing podcast functionality. The plan outlines a multi-phase implementation strategy addressing database models, feed parsing, synchronization pipelines, content fetching, metadata extraction, and user-facing features. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@docs/rss-feed-plan.md`:
- Around line 506-510: Add a language identifier to the fenced code block
containing the CLI output ("Podcasts: 12 (45 episodes indexed) ... - Pending
article fetch: 5") so markdownlint rule MD040 is satisfied; replace the opening
triple backticks with triple backticks followed by the language token (e.g.,
"text") in the fenced block that surrounds that output in docs/rss-feed-plan.md.
- Around line 250-256: Add a language identifier (e.g., "text") to the two
fenced code blocks containing the pipeline diagrams so they satisfy MD040;
update the block markers around the lines "Sync → Download → Transcribe →
[Post-process: Metadata → Index → Cleanup]" and "Sync → Fetch Article Content →
[Post-process: Metadata → Index]" to use ```text instead of ``` so markdownlint
stops flagging them.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/rss-feed-plan.md
🧰 Additional context used
🪛 markdownlint-cli2 (0.20.0)
docs/rss-feed-plan.md
[warning] 250-250: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
[warning] 255-255: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
[warning] 506-506: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
| ``` | ||
| Sync → Download → Transcribe → [Post-process: Metadata → Index → Cleanup] | ||
| ``` | ||
|
|
||
| For article feeds, the pipeline becomes: | ||
| ``` | ||
| Sync → Fetch Article Content → [Post-process: Metadata → Index] |
There was a problem hiding this comment.
Add a language to these fenced code blocks to satisfy MD040.
These blocks are missing a language identifier, which triggers markdownlint and can hurt rendering consistency.
✅ Suggested fix
-```
+```text
Sync → Download → Transcribe → [Post-process: Metadata → Index → Cleanup]
-```
+```
-```
+```text
Sync → Fetch Article Content → [Post-process: Metadata → Index]
-```
+```
</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)
[warning] 250-250: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
[warning] 255-255: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In `@docs/rss-feed-plan.md` around lines 250 - 256, Add a language identifier
(e.g., "text") to the two fenced code blocks containing the pipeline diagrams so
they satisfy MD040; update the block markers around the lines "Sync → Download →
Transcribe → [Post-process: Metadata → Index → Cleanup]" and "Sync → Fetch
Article Content → [Post-process: Metadata → Index]" to use ```text instead of
``` so markdownlint stops flagging them.
| ``` | ||
| Podcasts: 12 (45 episodes indexed) | ||
| Feeds: 3 (127 articles indexed) | ||
| - Pending article fetch: 5 | ||
| ``` |
There was a problem hiding this comment.
Add a language to this fenced block to satisfy MD040.
The CLI output snippet should declare a language to keep markdownlint happy and improve rendering.
✅ Suggested fix
-```
+```text
Podcasts: 12 (45 episodes indexed)
Feeds: 3 (127 articles indexed)
- Pending article fetch: 5
-```
+```
</details>
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.20.0)</summary>
[warning] 506-506: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
In @docs/rss-feed-plan.md around lines 506 - 510, Add a language identifier to
the fenced code block containing the CLI output ("Podcasts: 12 (45 episodes
indexed) ... - Pending article fetch: 5") so markdownlint rule MD040 is
satisfied; replace the opening triple backticks with triple backticks followed
by the language token (e.g., "text") in the fenced block that surrounds that
output in docs/rss-feed-plan.md.
</details>
<!-- fingerprinting:phantom:triton:eagle -->
<!-- This is an auto-generated comment by CodeRabbit -->
2 participants
Comprehensive plan for adding article feed support as a new content type
alongside podcasts. Covers database changes, feed detection, article
fetching, pipeline integration, search, email digests, and web UI.
https://claude.ai/code/session_01Yaeio8uaqmLiJnuhwHV1GY
Summary by CodeRabbit