From b82613384e9bd5fcac408c62092e076c239a90e8 Mon Sep 17 00:00:00 2001 From: Joshua Pozos <25085383+JoshuaPozos@users.noreply.github.com> Date: Sun, 10 May 2026 15:44:19 -0600 Subject: [PATCH] docs: request real WordPress WXR exports for pull-wordpress dogfood MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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]. --- CHANGELOG.md | 5 +++++ README.md | 14 ++++++++++++++ 2 files changed, 19 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1f5a6df..a5e571b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,11 @@ All notable changes to `content-model-simulator` are documented here. +## [Unreleased] + +### Changed +- **README and `example-wp-pull/` README** now explicitly request real-world WordPress WXR exports (especially with ACF, Polylang/WPML, WooCommerce, or custom Gutenberg blocks) for dogfooding `pull-wordpress` against production shapes. Synthetic fixtures only go so far — known edge cases (ACF repeaters / flexible content / post-object refs, real translation grouping, custom post types, WooCommerce taxonomies) are unlikely to surface without real data. Anonymized exports welcome. + ## [0.6.1] — 2026-05-10 ### Added diff --git a/README.md b/README.md index 5f1561d..6aab363 100644 --- a/README.md +++ b/README.md @@ -251,6 +251,20 @@ This tool was built and dogfooded across actual content modeling work: - **Existing Contentful space audits** — pulled schemas and entries from production spaces (verified against real spaces with 5,200+ entries and 23 content types) without modifying anything - **`contentful-migration` script previews** — migration files replayed locally to catch field-design mistakes before running them against a real environment +## Help wanted: real WordPress data (especially with ACF) + +`cms-sim pull-wordpress` ships in v0.6.1 with synthetic WXR fixtures and the [`example-wp-pull/`](../example-wp-pull/) walk-through (12 docs, Gutenberg + Classic bodies, 2 attachments, nested categories, a featured-image flow). That covers the common shapes but **misses edge cases that only show up in real production exports**: + +- **ACF (Advanced Custom Fields)** — repeaters, flexible content, post-object refs, gallery / image fields, conditional logic +- **Polylang / WPML** with real translation grouping (the synthetic fixture only exercises the per-doc language taxonomy) +- **Custom post types** + ACF combos +- **WooCommerce** product structures (product attributes, variations, custom taxonomies) +- **Gutenberg blocks beyond the basics** — custom blocks, embeds, columns, reusable blocks + +If you maintain a WordPress site and can share a WXR export (`wp-admin → Tools → Export → All content`), it would help shake out edge cases before they hit users. An **anonymized export is fine** — replace post bodies with lorem ipsum, scrub user emails / display names — the schema shape and meta keys are what matters. + +Drop the file in a [GitHub issue](https://github.com/JoshuaPozos/content-model-simulator/issues/new) with a short note about the plugins / post-types used (ACF? WooCommerce? Polylang?), a gist link, or any file-share. Thanks. + ## What this tool does NOT do - **Does NOT upload, create, or modify anything** in your Contentful space