ATSHIFT FEED BUILDER
atshift Feed Builder compatibility with REEID Translate
atshift Feed Builder compatibility with REEID Translate is being evaluated from available plugin evidence. Builds public RSS 2.0 and JSON Feed 1.1 feeds from structured WordPress data (posts, custom fields, and author profile data). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for atshift Feed Builder.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
atshift Feed Builder is documented in the Other category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How atshift Feed Builder compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Builds public RSS 2.0 and JSON Feed 1.1 feeds from structured WordPress data (posts, custom fields, and author profile data).
- Provides multiple feed configurations and separate editor flows to either replace a standard WordPress RSS feed or add a custom RSS 2.0 / JSON Feed 1.1 feed.
- Includes optional integrations for field-name sources from ACF / Secure Custom Fields, Meta Box, and Carbon Fields, while remaining independently usable for standard WordPress post data.
- Offers a public source-adapter API via the `atshift_feed_builder_source_adapters` filter, where third-party plugins can register selectable mapping sources by implementing `Atshift_Feed_Builder_Source_Adapter` (and optionally `Atshift_Feed_Builder_Manual_Source_Adapter` for manually entered keys).
- Implements privacy/safety controls for feed output: hard exclusion/blocking of authentication, session, token, capability, password, and other protected values; adapter contracts require returning only values intended for public feeds and validating manually entered keys.
- Provides feed delivery and caching behavior: stable item IDs plus ETag and Last-Modified headers, with anonymous responses using a shared cache and logged-in requests bypassing that cache using private/no-store response headers.
Distinctive features
Builds public RSS 2.0 and JSON Feed 1.1 feeds from structured WordPress data (posts, custom fields, and author profile data). Provides multiple feed configurations and separate editor flows to either replace a standard WordPress RSS feed or add a custom RSS 2.0 / JSON Feed 1.1 feed. Supports selecting public post types and mapping output fields using format-specific mappings (including standard output fields, fixed text, atshift Fields, post-author UPF, explicitly selected post_meta, and optional Pods API value sources). Includes optional integrations for field-name sources from ACF / Secure Custom Fields, Meta Box, and Carbon Fields, while remaining independently usable for standard WordPress post data. Offers a public source-adapter API via the `atshift_feed_builder_source_adapters` filter, where third-party plugins can register selectable mapping sources by implementing `Atshift_Feed_Builder_Source_Adapter` (and optionally `Atshift_Feed_Builder_Manual_Source_Adapter` for manually entered keys). Implements privacy/safety controls for feed output: hard exclusion/blocking of authentication, session, token, capability, password, and other protected values; adapter contracts require returning only values intended for public feeds and validating manually entered keys. Provides feed delivery and caching behavior: stable item IDs plus ETag and Last-Modified headers, with anonymous responses using a shared cache and logged-in requests bypassing that cache using private/no-store response headers.
CONTENT BOUNDARY
atshift Feed Builder capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
atshift Feed Builder and REEID Translate FAQ.
What does atshift Feed Builder do according to the available plugin evidence?
atshift Feed Builder has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for atshift Feed Builder?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for atshift Feed Builder?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate atshift Feed Builder in a multilingual WordPress workflow.
REEID documents atshift Feed Builder functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.