Skip to content

docs: update RSS wizard guides for auto-generated recipe IDs (#8cb82c2)#558

Open
Colin-XKL wants to merge 2 commits intodevfrom
doc-sync/rss-recipe-id-7897192575607688520
Open

docs: update RSS wizard guides for auto-generated recipe IDs (#8cb82c2)#558
Colin-XKL wants to merge 2 commits intodevfrom
doc-sync/rss-recipe-id-7897192575607688520

Conversation

@Colin-XKL
Copy link
Owner

@Colin-XKL Colin-XKL commented Feb 26, 2026

User description

What Changed 💡

  • Updated "Save Recipe" steps in html-to-rss.md, curl-to-rss.md, and search-to-rss.md (both en and zh).
  • Documented the auto-fill behavior for Recipe Unique IDs.
  • Added details about strict validation ([a-z0-9-]) and the new Refresh button.

Why 📖

Recent code changes ([#8cb82c2]) introduced auto-generation and strict validation for Recipe IDs in the RSS wizards, which requires documentation sync to guide users correctly.

Files Updated

File Changes
doc-site/src/content/docs/en/guides/advanced/html-to-rss.md Updated Step 4
doc-site/src/content/docs/en/guides/advanced/curl-to-rss.md Updated Step 4
doc-site/src/content/docs/en/guides/advanced/search-to-rss.md Updated Step 4
doc-site/src/content/docs/zh/guides/advanced/html-to-rss.md Updated Step 4 (Chinese)
doc-site/src/content/docs/zh/guides/advanced/curl-to-rss.md Updated Step 4 (Chinese)
doc-site/src/content/docs/zh/guides/advanced/search-to-rss.md Updated Step 4 (Chinese)

Verification 🔍

  • Build succeeds (pnpm build in doc-site)
  • Content verified in generated HTML
  • Links checked

PR created automatically by Jules for task 7897192575607688520 started by @Colin-XKL


PR Type

Documentation


Description

  • Updated Recipe ID documentation across RSS wizard guides

  • Added auto-fill behavior and format validation details

  • Documented refresh button functionality for ID regeneration

  • Synchronized changes across English and Chinese guides


Diagram Walkthrough

flowchart LR
  A["Recipe ID Field"] --> B["Auto-Fill from Title"]
  A --> C["Format Validation"]
  A --> D["Refresh Button"]
  B --> E["Updated Documentation"]
  C --> E
  D --> E
  E --> F["EN & ZH Guides"]
Loading

File Walkthrough

Relevant files
Documentation
curl-to-rss.md
Enhanced Recipe ID documentation with validation details 

doc-site/src/content/docs/en/guides/advanced/curl-to-rss.md

  • Replaced single-line Recipe ID description with detailed breakdown
  • Added Auto-Fill behavior explanation
  • Documented format validation rules [a-z0-9-]
  • Added Refresh button functionality details
+4/-1     
html-to-rss.md
Enhanced Recipe ID documentation with validation details 

doc-site/src/content/docs/en/guides/advanced/html-to-rss.md

  • Replaced single-line Recipe ID description with detailed breakdown
  • Added Auto-Fill behavior explanation
  • Documented format validation rules [a-z0-9-]
  • Added Refresh button functionality details
+4/-1     
search-to-rss.md
Enhanced Recipe ID documentation with validation details 

doc-site/src/content/docs/en/guides/advanced/search-to-rss.md

  • Replaced single-line Recipe ID description with detailed breakdown
  • Added Auto-Fill behavior explanation
  • Documented format validation rules [a-z0-9-]
  • Added Refresh button functionality details
+4/-1     
curl-to-rss.md
Enhanced Recipe ID documentation with validation details 

doc-site/src/content/docs/zh/guides/advanced/curl-to-rss.md

  • Replaced single-line Recipe ID description with detailed breakdown in
    Chinese
  • Added Auto-Fill behavior explanation with Chinese translations
  • Documented format validation rules [a-z0-9-]
  • Added Refresh button functionality details in Chinese
+4/-1     
html-to-rss.md
Enhanced Recipe ID documentation with validation details 

doc-site/src/content/docs/zh/guides/advanced/html-to-rss.md

  • Replaced single-line Recipe ID description with detailed breakdown in
    Chinese
  • Added Auto-Fill behavior explanation with Chinese translations
  • Documented format validation rules [a-z0-9-]
  • Added Refresh button functionality details in Chinese
+4/-1     
search-to-rss.md
Enhanced Recipe ID documentation with validation details 

doc-site/src/content/docs/zh/guides/advanced/search-to-rss.md

  • Replaced single-line Recipe ID description with detailed breakdown in
    Chinese
  • Added Auto-Fill behavior explanation with Chinese translations
  • Documented format validation rules [a-z0-9-]
  • Added Refresh button functionality details in Chinese
+4/-1     

Summary by Sourcery

Documentation:

  • Expand Recipe ID sections in HTML-to-RSS, cURL-to-RSS, and Search-to-RSS guides to cover auto-fill from title, allowed ID format, and the Refresh-based regeneration flow in both English and Chinese.

- Updated "Save Recipe" steps in `html-to-rss.md`, `curl-to-rss.md`, and `search-to-rss.md` (both `en` and `zh`).
- Documented the auto-fill behavior for Recipe Unique IDs.
- Added details about strict validation (`[a-z0-9-]`) and the new Refresh button.

Co-authored-by: Colin-XKL <49122401+Colin-XKL@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel
Copy link

vercel bot commented Feb 26, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
feed-craft-admin Ready Ready Preview, Comment Feb 26, 2026 6:09am
feed-craft-doc Ready Ready Preview, Comment Feb 26, 2026 6:09am

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Colin-XKL, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the documentation for the RSS wizard guides to align with recent changes in how Recipe Unique IDs are managed. The updates provide users with accurate information on the auto-generation, strict validation rules, and the new refresh functionality for these IDs, ensuring the guides reflect the current user experience.

Highlights

  • Documentation Updates: Updated the 'Save Recipe' steps across English and Chinese RSS wizard guides (html-to-rss.md, curl-to-rss.md, and search-to-rss.md).
  • Recipe ID Auto-Fill: Documented the new auto-fill behavior for Recipe Unique IDs, explaining how they are automatically populated from the feed title.
  • Validation and Refresh: Added details regarding the strict validation rules ([a-z0-9-]) for Recipe IDs and the functionality of the new Refresh button.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • doc-site/src/content/docs/en/guides/advanced/curl-to-rss.md
    • Updated the description for 'Recipe Unique ID' to include details on auto-fill behavior, allowed format, and the refresh button.
  • doc-site/src/content/docs/en/guides/advanced/html-to-rss.md
    • Updated the description for 'Recipe Unique ID' to include details on auto-fill behavior, allowed format, and the refresh button.
  • doc-site/src/content/docs/en/guides/advanced/search-to-rss.md
    • Updated the description for 'Recipe ID' to include details on auto-fill behavior, allowed format, and the refresh button.
  • doc-site/src/content/docs/zh/guides/advanced/curl-to-rss.md
    • Updated the Chinese description for '食谱唯一 ID (Recipe Unique ID)' to include details on auto-fill behavior, allowed format, and the refresh button.
  • doc-site/src/content/docs/zh/guides/advanced/html-to-rss.md
    • Updated the Chinese description for '食谱唯一 ID (Recipe Unique ID)' to include details on auto-fill behavior, allowed format, and the refresh button.
  • doc-site/src/content/docs/zh/guides/advanced/search-to-rss.md
    • Updated the Chinese description for '配方 ID (Recipe ID)' to include details on auto-fill behavior, allowed format, and the refresh button.
Activity
  • The pull request was automatically created by Jules for a task initiated by @Colin-XKL.
  • The build process successfully completed (pnpm build in doc-site).
  • The content was verified in the generated HTML output.
  • All links within the updated documentation were checked.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@qodo-code-review
Copy link
Contributor

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@qodo-code-review
Copy link
Contributor

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

PR Code Suggestions ✨

Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
Learned
best practice
Fix inconsistent localization wording

Use the same bilingual/translated UI label style as the other Chinese guides
(e.g., 自定义食谱 (Custom Recipes)) instead of leaving Custom Recipes untranslated in
the middle of a Chinese sentence.

doc-site/src/content/docs/zh/guides/advanced/search-to-rss.md [53]

-保存后,该配方将作为 **自定义配方 (Custom Recipe)** 存储。你可以在 **Custom Recipes** 仪表板中管理它。
+保存后,该配方将作为 **自定义配方 (Custom Recipe)** 存储。你可以在 **自定义食谱 (Custom Recipes)** 仪表板中管理它。

[To ensure code accuracy, apply this suggestion manually]

Suggestion importance[1-10]: 6

__

Why:
Relevant best practice - Keep localization consistent within a given language document (avoid mixing untranslated UI labels unexpectedly).

Low
Standardize recipe ID terminology

Align the placeholder name with the label used earlier in the guide (Recipe ID)
by using a consistent placeholder (or rename the step to Recipe Unique ID).

doc-site/src/content/docs/en/guides/advanced/search-to-rss.md [55-56]

 Your new feed will be available at:
-`http://your-feedcraft-instance/rss/custom/{recipe-unique-id}`
+`http://your-feedcraft-instance/rss/custom/{recipe-id}`

[To ensure code accuracy, apply this suggestion manually]

Suggestion importance[1-10]: 5

__

Why:
Relevant best practice - Keep documentation terminology and placeholders consistent to avoid confusing readers.

Low
  • More

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the documentation for the RSS wizard guides to reflect new features for the 'Recipe Unique ID', including auto-generation, format validation, and a refresh button. The changes are applied consistently across English and Chinese versions of the html-to-rss, curl-to-rss, and search-to-rss guides.

My review focuses on improving documentation consistency. I've suggested aligning the terminology for the recipe identifier in the search-to-rss.md guides (both English and Chinese) with other guides and with URL placeholders within the same files. This will help prevent user confusion.

Comment on lines +44 to +47
1. **Recipe ID**: Choose a unique identifier for this recipe (e.g., `search-ai-news`).
- **Auto-Fill**: This field is automatically populated from the feed title.
- **Format**: Only lowercase letters, numbers, and hyphens (`[a-z0-9-]`) are allowed.
- **Refresh**: You can manually regenerate the ID from the title using the refresh button.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency with other guides (like curl-to-rss.md) and the URL placeholder {recipe-unique-id} on line 56, consider renaming Recipe ID to Recipe Unique ID. This will improve clarity for users.

Suggested change
1. **Recipe ID**: Choose a unique identifier for this recipe (e.g., `search-ai-news`).
- **Auto-Fill**: This field is automatically populated from the feed title.
- **Format**: Only lowercase letters, numbers, and hyphens (`[a-z0-9-]`) are allowed.
- **Refresh**: You can manually regenerate the ID from the title using the refresh button.
1. **Recipe Unique ID**: Choose a unique identifier for this recipe (e.g., `search-ai-news`).
- **Auto-Fill**: This field is automatically populated from the feed title.
- **Format**: Only lowercase letters, numbers, and hyphens (`[a-z0-9-]`) are allowed.
- **Refresh**: You can manually regenerate the ID from the title using the refresh button.

Comment on lines +44 to +47
1. **配方 ID (Recipe ID)**:为此配方选择一个唯一的标识符(例如 `search-ai-news`)。
- **自动填充 (Auto-Fill)**:该字段将根据订阅源标题自动填充。
- **格式 (Format)**:仅允许小写字母、数字和连字符 (`[a-z0-9-]`)。
- **刷新 (Refresh)**:你可以使用刷新按钮根据标题手动重新生成 ID。
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency with other guides (e.g., curl-to-rss.md) and the URL placeholder {recipe-unique-id} on line 56, consider renaming 配方 ID (Recipe ID) to 食谱唯一 ID (Recipe Unique ID). This also involves changing 配方 to 食谱 in the description to align terminology across all Chinese documentation.

Suggested change
1. **配方 ID (Recipe ID)**为此配方选择一个唯一的标识符(例如 `search-ai-news`)。
- **自动填充 (Auto-Fill)**:该字段将根据订阅源标题自动填充。
- **格式 (Format)**:仅允许小写字母、数字和连字符 (`[a-z0-9-]`)。
- **刷新 (Refresh)**:你可以使用刷新按钮根据标题手动重新生成 ID。
1. **食谱唯一 ID (Recipe Unique ID)**为此食谱选择一个唯一的标识符(例如 `search-ai-news`)。
- **自动填充 (Auto-Fill)**:该字段将根据订阅源标题自动填充。
- **格式 (Format)**:仅允许小写字母、数字和连字符 (`[a-z0-9-]`)。
- **刷新 (Refresh)**:你可以使用刷新按钮根据标题手动重新生成 ID。

@coderabbitai
Copy link

coderabbitai bot commented Feb 26, 2026

Walkthrough

This PR updates documentation in six guides (English and Chinese versions) to explicitly describe the Recipe Unique ID field's auto-fill, format constraints, and refresh capabilities in the Save Recipe step, replacing implicit behavior descriptions with detailed itemized documentation.

Changes

Cohort / File(s) Summary
English Guides
doc-site/src/content/docs/en/guides/advanced/curl-to-rss.md, html-to-rss.md, search-to-rss.md
Expanded Recipe Unique ID documentation from single-line description to structured block documenting Auto-Fill (from feed title), Format (a-z0-9-), and Refresh (regenerate via button).
Chinese Guides
doc-site/src/content/docs/zh/guides/advanced/curl-to-rss.md, html-to-rss.md, search-to-rss.md
Expanded Recipe Unique ID documentation from single-line description to structured block documenting Auto-Fill (from feed title), Format (a-z0-9-), and Refresh (regenerate via button).

Possibly related PRs

Poem

📚 A rabbit hops through guides with glee,
Documenting ID fields for all to see—
Auto-fill, format, refresh with care,
Clear instructions floating in the air! 🐰✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: updating documentation for RSS wizard guides to reflect auto-generated recipe ID functionality.
Description check ✅ Passed The description comprehensively explains what changed, why the changes were needed, which files were updated, and includes verification details—all directly related to the documentation updates in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch doc-sync/rss-recipe-id-7897192575607688520

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented Feb 26, 2026

Reviewer's Guide

Updates RSS wizard documentation in both English and Chinese guides to describe the new Recipe ID behavior, including auto-fill from title, strict ID format validation, and the manual refresh/regeneration option in the “Save Recipe” step across HTML-to-RSS, cURL-to-RSS, and Search-to-RSS flows.

Sequence diagram for Recipe ID auto-fill and validation in RSS wizard

sequenceDiagram
  actor User
  participant WizardUI
  participant RecipeIdField
  participant ValidationEngine

  User->>WizardUI: Open_RSS_wizard
  WizardUI->>RecipeIdField: Initialize_field

  User->>WizardUI: Enter_feed_title
  WizardUI->>RecipeIdField: Auto_fill_from_title

  User->>RecipeIdField: Edit_Recipe_ID_optional
  RecipeIdField->>ValidationEngine: Validate_ID_value
  ValidationEngine-->>RecipeIdField: Result_valid_or_error

  User->>RecipeIdField: Click_refresh_button
  RecipeIdField->>WizardUI: Request_title_value
  WizardUI-->>RecipeIdField: Title_value
  RecipeIdField->>RecipeIdField: Regenerate_ID_from_title
  RecipeIdField->>ValidationEngine: Validate_regenerated_ID
  ValidationEngine-->>RecipeIdField: Result_valid

  User->>WizardUI: Click_confirm_and_save
  WizardUI->>ValidationEngine: Final_ID_validation
  ValidationEngine-->>WizardUI: Validation_passed
  WizardUI-->>User: Recipe_saved_successfully
Loading

File-Level Changes

Change Details Files
Expand Recipe ID field description in EN RSS wizard guides to cover auto-fill, validation, and refresh behavior.
  • Replace the previous single-sentence Recipe ID description with a labeled field plus nested bullets.
  • Add an explicit note that the Recipe ID auto-fills from the feed title instead of conditionally generating only when empty.
  • Document the allowed Recipe ID character set as lowercase letters, digits, and hyphens using the [a-z0-9-] pattern.
  • Describe the new refresh button that regenerates the ID from the title.
doc-site/src/content/docs/en/guides/advanced/html-to-rss.md
doc-site/src/content/docs/en/guides/advanced/curl-to-rss.md
doc-site/src/content/docs/en/guides/advanced/search-to-rss.md
Mirror the enhanced Recipe ID documentation in the corresponding ZH RSS wizard guides.
  • Update the Chinese Recipe ID description to match the new English structure with main bullet plus sub-bullets.
  • Localize explanations for auto-fill from title, strict format validation, and the refresh/regeneration button.
  • Ensure terminology for Recipe Unique ID, Auto-Fill, Format, and Refresh is consistently bilingual where appropriate.
doc-site/src/content/docs/zh/guides/advanced/html-to-rss.md
doc-site/src/content/docs/zh/guides/advanced/curl-to-rss.md
doc-site/src/content/docs/zh/guides/advanced/search-to-rss.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • In the Search-to-RSS guides (EN and ZH), the updated Recipe ID section no longer mentions that the ID becomes part of the feed URL; if that behavior is still correct, consider keeping a short note about the URL impact to help users choose IDs carefully.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- In the Search-to-RSS guides (EN and ZH), the updated Recipe ID section no longer mentions that the ID becomes part of the feed URL; if that behavior is still correct, consider keeping a short note about the URL impact to help users choose IDs carefully.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (1)
doc-site/src/content/docs/en/guides/advanced/search-to-rss.md (1)

44-47: Consider aligning the label to “Recipe Unique ID” for cross-guide consistency.

This page uses Recipe ID, while related guides use Recipe Unique ID. Using the same label everywhere would reduce ambiguity.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@doc-site/src/content/docs/en/guides/advanced/search-to-rss.md` around lines
44 - 47, Update the label text "Recipe ID" to "Recipe Unique ID" (and adjust the
related inline descriptions "Auto-Fill", "Format", "Refresh" if they reference
the old label) so this guide matches the naming used across related guides;
search for the literal string "Recipe ID" (and the example `search-ai-news`) in
this document and replace it with "Recipe Unique ID", ensuring the description
about auto-population, allowed format `[a-z0-9-]`, and the refresh behavior
remain accurate and consistent.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@doc-site/src/content/docs/en/guides/advanced/curl-to-rss.md`:
- Around line 66-69: Add the same "Recipe Unique ID" guidance to the Traditional
Chinese (zh-tw) version of the same guide: mirror the four bullet points
("Recipe Unique ID", "Auto-Fill", "Format", "Refresh") with equivalent zh-tw
wording and keep the formatting (code span for `[a-z0-9-]`) and examples (e.g.,
`my-custom-api-feed`); ensure the zh-tw curl-to-rss guide contains the exact
behavior notes about auto-population from the title, allowed characters, and the
manual refresh button so en/zh/zh-tw are synchronized.

In `@doc-site/src/content/docs/zh/guides/advanced/curl-to-rss.md`:
- Around line 66-69: Replace the incorrect Chinese term "食谱" with the required
project term "配方" in the doc content where the heading and related lines use
"**食谱唯一 ID (Recipe Unique ID)**" — update that heading and any inline
occurrences (e.g., the lines describing Auto-Fill, Format, Refresh) so they read
"**配方唯一 ID (Recipe Unique ID)**" and maintain the existing English
parenthetical; ensure consistency with other docs using "Recipe (配方)".

In `@doc-site/src/content/docs/zh/guides/advanced/html-to-rss.md`:
- Around line 64-67: The documentation block uses the term "食谱唯一 ID" which
violates the repository terminology rule requiring "配方" for Recipe; update the
phrase and any adjacent occurrences (e.g., the header and the "自动填充", "格式", and
"刷新" lines) to use "配方唯一 ID" and ensure the nearby Save button/text also uses
"配方" instead of "食谱"; review the surrounding paragraphs in the same section to
replace any other instances of "食谱" with "配方" so the doc consistently uses the
designated term.

---

Nitpick comments:
In `@doc-site/src/content/docs/en/guides/advanced/search-to-rss.md`:
- Around line 44-47: Update the label text "Recipe ID" to "Recipe Unique ID"
(and adjust the related inline descriptions "Auto-Fill", "Format", "Refresh" if
they reference the old label) so this guide matches the naming used across
related guides; search for the literal string "Recipe ID" (and the example
`search-ai-news`) in this document and replace it with "Recipe Unique ID",
ensuring the description about auto-population, allowed format `[a-z0-9-]`, and
the refresh behavior remain accurate and consistent.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8cb82c2 and 916ba20.

📒 Files selected for processing (6)
  • doc-site/src/content/docs/en/guides/advanced/curl-to-rss.md
  • doc-site/src/content/docs/en/guides/advanced/html-to-rss.md
  • doc-site/src/content/docs/en/guides/advanced/search-to-rss.md
  • doc-site/src/content/docs/zh/guides/advanced/curl-to-rss.md
  • doc-site/src/content/docs/zh/guides/advanced/html-to-rss.md
  • doc-site/src/content/docs/zh/guides/advanced/search-to-rss.md

Comment on lines +66 to +69
- **Recipe Unique ID**: A unique identifier for this feed configuration (e.g., `my-custom-api-feed`).
- **Auto-Fill**: This field is automatically populated from the feed title.
- **Format**: Only lowercase letters, numbers, and hyphens (`[a-z0-9-]`) are allowed.
- **Refresh**: You can manually regenerate the ID from the title using the refresh button.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Please sync this new Recipe ID guidance to zh-tw docs in the same PR.

The update is mirrored in en/zh, but this task also requires zh-tw parity for the same guides. Please add equivalent zh-tw updates for these Recipe ID behavior changes before merge.

Based on learnings, "FeedCraft documentation MUST be kept in sync across all supported languages (en, zh, zh-tw). Every single update or modification MUST be applied to ALL language versions in the same turn/task."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@doc-site/src/content/docs/en/guides/advanced/curl-to-rss.md` around lines 66
- 69, Add the same "Recipe Unique ID" guidance to the Traditional Chinese
(zh-tw) version of the same guide: mirror the four bullet points ("Recipe Unique
ID", "Auto-Fill", "Format", "Refresh") with equivalent zh-tw wording and keep
the formatting (code span for `[a-z0-9-]`) and examples (e.g.,
`my-custom-api-feed`); ensure the zh-tw curl-to-rss guide contains the exact
behavior notes about auto-population from the title, allowed characters, and the
manual refresh button so en/zh/zh-tw are synchronized.

Comment on lines +66 to +69
- **食谱唯一 ID (Recipe Unique ID)**:此订阅源配置的唯一标识符(例如 `my-custom-api-feed`)。
- **自动填充 (Auto-Fill)**:该字段将根据订阅源标题自动填充。
- **格式 (Format)**:仅允许小写字母、数字和连字符 (`[a-z0-9-]`)。
- **刷新 (Refresh)**:你可以使用刷新按钮根据标题手动重新生成 ID。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Please replace “食谱” with the required “配方” terminology here.

The new 食谱唯一 ID wording conflicts with the project’s required Recipe terminology (配方).

As per coding guidelines, "Use 'AtomCraft' (原子工藝/原子工艺), 'FlowCraft' (組合工藝/组合工艺), and 'Recipe' (配方) consistently across all documentation."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@doc-site/src/content/docs/zh/guides/advanced/curl-to-rss.md` around lines 66
- 69, Replace the incorrect Chinese term "食谱" with the required project term
"配方" in the doc content where the heading and related lines use "**食谱唯一 ID
(Recipe Unique ID)**" — update that heading and any inline occurrences (e.g.,
the lines describing Auto-Fill, Format, Refresh) so they read "**配方唯一 ID (Recipe
Unique ID)**" and maintain the existing English parenthetical; ensure
consistency with other docs using "Recipe (配方)".

Comment on lines +64 to +67
- **食谱唯一 ID (Recipe Unique ID)**:此订阅源配置的唯一标识符(例如 `tech-blog-feed`)。
- **自动填充 (Auto-Fill)**:该字段将根据订阅源标题自动填充。
- **格式 (Format)**:仅允许小写字母、数字和连字符 (`[a-z0-9-]`)。
- **刷新 (Refresh)**:你可以使用刷新按钮根据标题手动重新生成 ID。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Use the required “配方” term consistently in this new block.

This changed section uses 食谱唯一 ID, which conflicts with the repository terminology rule for Recipe (配方). Please align this block (and nearby Save text) to 配方.

As per coding guidelines, "Use 'AtomCraft' (原子工藝/原子工艺), 'FlowCraft' (組合工藝/组合工艺), and 'Recipe' (配方) consistently across all documentation."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@doc-site/src/content/docs/zh/guides/advanced/html-to-rss.md` around lines 64
- 67, The documentation block uses the term "食谱唯一 ID" which violates the
repository terminology rule requiring "配方" for Recipe; update the phrase and any
adjacent occurrences (e.g., the header and the "自动填充", "格式", and "刷新" lines) to
use "配方唯一 ID" and ensure the nearby Save button/text also uses "配方" instead of
"食谱"; review the surrounding paragraphs in the same section to replace any other
instances of "食谱" with "配方" so the doc consistently uses the designated term.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant