feat: update feed names to be more human-readable and personal

[dubadub]

Updated all generic feed titles (like "username/repo recipes") with more descriptive and personalized names based on repository READMEs and descriptions. This makes the feed list more user-friendly and easier to browse.

Changes include:

• Adding author names to feed titles for personalization
• Using descriptions from READMEs where available
• Making titles more descriptive and meaningful

[claude]

Pull Request Review: Update Feed Names

Summary

This PR updates 23 feed titles to be more human-readable and personalized. Overall, this is a positive improvement that enhances UX by making feed titles more descriptive and easier to browse.

Positive Aspects ✅

1. Clear Intent: The PR has a well-defined goal of improving user experience by making feed titles more descriptive
2. Consistent Approach: Most changes follow a consistent pattern of personalizing titles with author names
3. Better Discoverability: More descriptive titles help users quickly identify content sources
4. Non-Breaking Change: This is purely a content/metadata update with zero code changes

Issues & Concerns 🔍

1. Inconsistent Capitalization Patterns

The changes introduce inconsistent capitalization across the file:

• config/feeds.yaml:51 - "LiHRaM's Cooklang Recipe Collection"
• config/feeds.yaml:63 - "andoriyu's CookLang Recipe Collection"
• config/feeds.yaml:255 - "pakohan's Cooklang Recipe Collection"
• config/feeds.yaml:279 - "Mike Egan's CookLang Recipes"

Recommendation: The official brand name appears to be "Cooklang" (lowercase 'lang'). All instances should be consistent. Looking at the repository context and README, "Cooklang" seems to be the correct spelling.

2. Potential Factual Accuracy Issues

Some new titles make claims about content that should be verified:

• config/feeds.yaml:603 - "Brendan McKenzie's Multi-Cuisine Recipes"
• config/feeds.yaml:135 - "Ignacio's Cooking Notes & Recipes"
• config/feeds.yaml:159 - "cco2's Cooking Notes & Recipes"

Question: Were these descriptions verified against the actual repository content? If these are inferred rather than based on README/description, they could be misleading.

3. Mixed Naming Conventions

The file now has inconsistent title patterns:

• Possessive with full name: "Marcus Olsson's Recipe Collection" (line 387)
• Possessive with first name only: "Mike Egan's CookLang Recipes" (line 279)
• Username possessive: "andoriyu's CookLang Recipe Collection" (line 63)
• No possessive: "Tasty Eats: Community Recipe Collection" (line 711)

Recommendation: While some variation is natural, establishing clearer guidelines for title formatting would improve consistency. Consider:

• When to use full names vs. usernames vs. first names
• Whether to always include possessive form
• Standard suffixes ("Collection" vs "Recipes" vs "Repository")

4. Validation Concerns

Question: How were these new titles determined? From the PR description: "based on repository READMEs and descriptions"

• Was this done manually or automated?
• Were all 23 repositories reviewed?
• What happens when READMEs change - will titles be kept in sync?

This raises a maintenance concern - titles could become stale over time.

Recommendations 📋

High Priority

1. Fix capitalization: Standardize "Cooklang" vs "CookLang" throughout the file
2. Verify accuracy: Confirm that descriptive titles match actual repository content

Medium Priority

3. Document guidelines: Add a comment in feeds.yaml or update config/README.md with title formatting guidelines
4. Consider automation: If titles are based on README content, consider automating this to keep them in sync

Low Priority

5. Consistency pass: Do a full review of ALL titles in the file (not just the 23 changed) to ensure consistent formatting

Testing Checklist ✓

• Verify YAML syntax is valid (should be caught by CI)
• Confirm no duplicate URLs introduced (should be caught by CI)
• Manual review: Open 3-5 of the changed repository URLs to verify new titles are accurate
• Check if any titles exceed reasonable length limits for UI display

Security & Performance

• ✅ No security concerns (content-only change)
• ✅ No performance impact
• ✅ No breaking changes

Conclusion

This PR is a net positive that improves UX. However, it would benefit from:

1. Fixing the capitalization inconsistencies
2. Verifying factual accuracy of new descriptions
3. Establishing clearer title formatting guidelines for future contributions

The changes are safe to merge after addressing the capitalization issue. The other concerns are more about long-term maintainability and consistency.

Status: Approve with minor changes requested (fix capitalization)

---

Review generated by Claude Code