This file defines the source list and source-selection rules.
A source belongs in this project if it:
- publishes WordPress developer-relevant updates
- has an RSS feed or predictable public URL
- produces information that can affect real development decisions
- can be cited in a public report
A source should be excluded if it is mostly:
- marketing
- rumors
- drama
- duplicate commentary
- too broad to be useful
- unsupported claims
Phase 1 started with Tier 1 only. As of v0.1.3, Tier 2 sources are included in the default collection.
Why included: Developer-facing updates, APIs, block editor guidance, and official educational content.
Why included: Core development activity, release planning, technical proposals, and dev notes.
Why included: Official release and ecosystem updates.
- URL: https://www.advancedcustomfields.com/blog/
- Feed: https://www.advancedcustomfields.com/blog/feed/
Why included: ACF-specific developer workflow updates and modern WordPress implementation patterns.
Included in the default collection since v0.1.3. The collector fetches all sources (Tier 1 + Tier 2) by default.
Why included: Curated Gutenberg ecosystem coverage and community perspective.
- URL: https://www.advancedcustomfields.com/blog/tag/acf-chat-fridays/
- Feed: https://www.advancedcustomfields.com/blog/tag/acf-chat-fridays/feed/
Why included: Community discussion and emerging ACF-related topics that may not appear in official docs yet.
Phase 1 started with Tier 1 only. Tier 2 sources (Gutenberg Times, ACF Chat Fridays) were added once the core workflow was proven.
To customize the source list, copy sources.example.yaml to sources.yaml and edit. The collector reads from sources.yaml if it exists, otherwise uses the built-in defaults.
cp sources.example.yaml sources.yamlEach source needs:
id— unique identifiername— display namefeedUrl— RSS feed URL
Optional:
url— homepage URLtier— 1 or 2 (default 2)