Content Review Workflow — AI Sync

How to compare each WordPress page against its Drupal source, fix or flag what's off, and record that a page has been reviewed. WordPress Admin → Drupal Sync → AI Sync tab.

The flow at a glance

1 · Open AI Sync→ 2 · Pick type + language→ 3 · Preview Pages→ 4 · Calculate Diff→ 5 · Open diff details→ 6 · Fix / apply text→ 7 · Tag issues or Mark clean

The golden rule: every page you look at should end in one of two states — either it carries one or more issue tags (something to fix), or it's marked ✓ Clean (checked, nothing wrong). A page that is neither hasn't been reviewed yet.

Step by step

1

Open the AI Sync tab

In WordPress admin, go to Drupal Sync and click the AI Sync tab. This is where all comparison and review work happens.

2

Choose a post type and language

Set Post type (e.g. Page or Resource) and Language (EN, FR, DE, ES, IT). You review one post type + one language at a time — that keeps the list focused and lets each teammate own a slice of the work.

3

Load the list — Preview Pages

Click Preview Pages. The table lists every page of that type/language, side by side: WordPress title & path next to the matched Drupal title & path, plus status columns.

Use the filters above the table to cut noise:

  • Hide pages with no Drupal translation — on by default; hides pages that don't exist in Drupal for this language, so you only see real work.
  • Hide No UUID rows — hides WordPress-only pages that have no Drupal counterpart at all.
  • Search, Sort, and Min Diff % — narrow the list further once diffs are calculated.

Missing WordPress page? If a row shows the translation doesn't exist yet, use the row's Create button (or Create Missing WP Translations below the table) to make the WordPress translation before reviewing it.

4

Calculate the diff

Click 📊 Calculate Diff (visible) to compare every visible row's WordPress content against its Drupal source. Each row then shows a Diff % badge — higher means more drift from Drupal. To refresh a single row, click the 🔃 icon next to its badge.

If a badge shows it's out of date (the page was edited after the diff ran), just recalculate it before reviewing.

5

Open the diff details

Click the Diff % badge to open the details popover. Differences are grouped so you can see exactly what's off:

  • Changed — text that exists on both sides but doesn't match.
  • Only in WP — text present in WordPress but not in Drupal.
  • Only in Drupal — text in Drupal that's missing from WordPress.
  • Ignored items — differences you've dismissed; they no longer count toward the score.
6

Act on the differences

Inside the details popover you can:

  • Apply Drupal text → — pull Drupal's version of a changed line straight into the WordPress element.
  • 🚫 Ignore / 🚫 Ignore all — dismiss differences that aren't real problems (dynamic lists, forms, query loops), so they stop inflating the Diff %.
  • 🏷 Mark as false positive — when a whole page's high score comes from content the sync intentionally skips. The number stays visible (struck through) but is excluded from filters.
  • Recalculate — re-run the diff after making changes.

Anything that needs a real content or layout fix in WordPress, fix it in the page (Bricks) as usual — then record it in the next step.

7

Record your review — tag issues or mark clean

At the bottom of the same popover is the review panel. This is how the team tracks what's been checked:

  • Found a problem? Pick an issue tag from the dropdown (meanings below), add an optional note (e.g. "hero image missing"), and click + Add tag. Add as many as apply.
  • Page looks correct? Click ✓ No issues (mark clean). It records who checked it and when.

Your tags (or a green ✓ Clean mark) then show in the Review Tags column back on the table, so anyone can see a page's status at a glance. Remove a tag with its ×, or clear the clean mark, any time.

Adding a tag automatically clears a "clean" mark, and vice-versa — a page is either clean or has issues, never both. Fixed everything and re-checked? Remove the tags and mark it clean.

What each issue tag means

Pick the tag that best describes the problem so the whole team classifies issues the same way. (These same descriptions appear as tooltips inside the plugin.)

TagUse it when…
Translation Text is present but the translation is wrong, incomplete, or still in English — mistranslations, untranslated strings, or inconsistent terminology.
Missing content Content that exists on the Drupal (source) page is absent in WordPress — dropped sections, paragraphs, images, links, or whole blocks.
Layout / styling Content is correct but its presentation differs — spacing, fonts, colours, broken columns, misaligned or overflowing elements, responsive issues.
Discrepancy / error A factual or functional mismatch not covered by the other tags — wrong values or data, broken links, or an outright error on the page.

Reading the table — quick reference

ColumnWhat it tells you
WP / Drupal Title & PathThe WordPress page and the Drupal source it was matched to, side by side.
StatusWhether a Drupal match was found for this language.
WP Trans.Whether the translated WordPress page exists yet (offers a Create button if not).
Last Sync / PICWhen the page was last synced and who did it.
Diff %How far WordPress has drifted from Drupal. Click the badge for details.
Diff PICWho last calculated the diff on that row.
Review TagsYour issue tags, or the green ✓ Clean mark. Empty = not reviewed yet.

Good habits

  1. Own a slice. Split work by post type + language so two people don't review the same pages.
  2. Always land in a final state. Every page you touch ends up tagged or clean — that's how we know it's been checked.
  3. Add a short note when tagging. "Missing pricing table" is far more useful to whoever fixes it than a bare tag.
  4. Trim the noise. Ignore or mark false-positive the differences that aren't real, so Diff % stays meaningful.
  5. Recalculate after fixing so the score reflects the current page before you mark it clean.

Drupal Content Sync · AI Sync review workflow · for the content team