docs: request real WordPress WXR exports for pull-wordpress dogfood#14
Merged
Conversation
v0.6.1 shipped pull-wordpress with synthetic fixtures only. Real WordPress production exports — especially with ACF (repeaters, flexible content, post-object refs, gallery), Polylang/WPML with actual translation grouping, custom post types, WooCommerce, or custom Gutenberg blocks — almost certainly carry edge cases the synthetic 12-doc fixture doesn't. Adds a "Help wanted: real WordPress data (especially with ACF)" section to the main README right above "What this tool does NOT do", pointing at the GitHub issues URL and listing what to share (an anonymized WXR is fine — schema shape and post-meta keys matter, content doesn't). Extends `example-wp-pull/README.md` "Limitations / follow-ups" with the same ask, scoped to the example's audience. Both surfaces explain what to anonymize (post bodies, emails, display names) and what to preserve (schema shape, post-meta keys, plugin-specific conventions). Goal: surface bug reports during the v0.6.x reposo window before v0.7.0 work starts. No code changes. CHANGELOG entry under [Unreleased].
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
example-wp-pull/README.md"Limitations / follow-ups" with the same ask.[Unreleased]entry.Why
v0.6.1 shipped
pull-wordpresswith synthetic WXR fixtures only. Real production exports — especially with ACF (repeaters / flexible content / post-object refs / gallery), Polylang or WPML with actual translation grouping, custom post types + ACF combos, WooCommerce, or custom Gutenberg blocks — almost certainly carry edge cases the 12-document synthetic fixture doesn't. Surfacing the ask in two visible places (npm README + example README) gives the v0.6.x reposo window a chance to collect community data before v0.7.0 work starts.What contributors are asked to share
wp-admin → Tools → Export → All contentOpen a GitHub issue, share a gist, or any file-share.
Test plan
Merge note
Plain docs PR. Squash or merge — your call. No tag, no GitHub Release, no version bump. Visible on github.com immediately; visible on npmjs.com next patch release (v0.6.2 or v0.7.0, whenever).