Content Review — Assessment Phase

Go through every WordPress page, compare it against its Drupal source, and log what's wrong — without fixing anything yet. WordPress Admin → Drupal Sync → AI Sync tab.

Check & log · no fixes yet

What this phase is for

We're surveying, not repairing. The job right now is to look at each page, decide whether it's fine or has problems, and tag those problems clearly. The output is a complete, tagged inventory across every page — that inventory is what tells us how much fix work is coming and what kind, so we can plan and assign it.

Please don't fix pages during this pass. Don't edit content, don't apply changes, don't create missing pages. If you start fixing, we lose an accurate picture of the total workload. Just check and log — fixing is a later, planned phase.

The flow at a glance

1 · Open AI Sync→ 2 · Pick type + language→ 3 · Preview Pages→ 4 · Calculate Diff→ 5 · Review the differences→ 6 · 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 later), or it's marked ✓ Clean (checked, nothing wrong). A page that is neither hasn't been reviewed yet.

Step by step

Open the AI Sync tab

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

Choose a post type and language

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

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.

WordPress page doesn't exist yet? If a row shows the translation is missing, that's a finding in itself — note it and flag it to your lead. Don't create the page during this pass.

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, which usually means more to check. To refresh a single row, click the 🔃 icon next to its badge.

If a badge shows it's out of date (the page changed after the diff ran), recalculate that row so your read reflects the current page.

Review the differences

Click the Diff % badge to open the details popover. This is your read-only view of exactly what differs, so you can classify the page. Differences are grouped:

Changed — text that exists on both sides but doesn't match (often a translation issue).
Only in WP — text present in WordPress but not in Drupal.
Only in Drupal — text in Drupal that's missing from WordPress (often missing content).

Also eyeball the live pages where useful (open the WordPress and Drupal paths in new tabs) to catch layout and visual problems the text diff can't see.

You're only reading here. Don't apply, ignore, or change anything — just note what's off and move to the next step to record it.

Record your assessment — tag issues or mark clean

At the bottom of the same popover is the review panel. This is how we build the inventory:

Found a problem? Pick an issue tag from the dropdown (meanings below), add a short note describing it (e.g. "hero image missing"), and click + Add tag. Add as many tags 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.

A page is either clean or has issues, never both — adding a tag clears a clean mark, and vice-versa. Your notes here become the actual work items we scope for the fix phase, so make them specific.

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.)

Tag	Use 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

Column	What it tells you
WP / Drupal Title & Path	The WordPress page and the Drupal source it was matched to, side by side.
Status	Whether a Drupal match was found for this language.
WP Trans.	Whether the translated WordPress page exists yet. If not, that's a finding to note.
Last Sync / PIC	When the page was last synced and who did it.
Diff %	How far WordPress has drifted from Drupal. Click the badge to see the details.
Diff PIC	Who last calculated the diff on that row.
Review Tags	Your issue tags, or the green ✓ Clean mark. Empty = not reviewed yet.

Good habits for this phase

Own a slice. Split work by post type + language so two people don't survey the same pages.
Always land in a final state. Every page you touch ends up tagged or clean — that's how we know it's been checked and how we measure coverage.
Write a specific note on every tag. "Missing pricing table in section 2" becomes a clear work item; a bare tag doesn't.
When in doubt, tag it. If you're unsure whether something's a real problem, tag it with a note and let the lead triage. Better logged than missed.
Don't fix. Resist editing pages — this pass is only to size the work. Fixing comes later, as a planned phase.

Drupal Content Sync · AI Sync — assessment phase · for the content team