The main migration decisions
Most editorial content has a suitable core block or FYE composition. Resolve the following layout and service decisions before bulk conversion, because they affect page templates, content modeling and dependencies.
- Section navigation: choose curated header menus or preserve the automatic page tree with a maintained component. Sticky Nav serves on-page sections and does not replace the hierarchy.
- Standard / Academic Unit layouts: agree whether to retain sidebars. If retained, build reusable page compositions and check mobile reading order; no matching ready-made templates are shown.
- People directory: keep an external integration or migrate people into a local post type with taxonomies and bio templates. Content Query becomes a candidate only after that data decision.
- RDC media hero: image-only can use Primary or Secondary header. Video requires a separately composed hero or extension; the destination header fields do not include the source video/poster model.
- Calendars and equipment forms: separate event teasers from full calendars, submissions and booking workflows. Preserve service identities and test the entire workflow, including confirmations.
- Shared content: replace reusable sidebar/table references with intentional shared content such as synced patterns. Decide which edits should propagate across pages or sites.
Suggested page recipes
These are proposed compositions using the documented destination pieces, not existing named FYE templates. Sidebar and directory recipes require additional implementation.
Standard information page
If automatic section navigation and sidebars must stay, add a custom layout instead of assuming the default page reproduces them.
Landing page
Preserve each source slab’s order, headline and CTA. Use Cover for image-overlay callouts; choose Swipe and Expanders only when the content merits those interactions.
Academic unit home
Keep the wide-area slabs after the main region. A reusable department-home pattern can capture this sequence once navigation and sidebar requirements are settled.
RDC homepage
Preserve the large-media intent and booking workflows. RDC’s red/yellow/blue schemes and geometric textures do not transfer as style names; select FYE brand colors deliberately.
Useful corrections to the guides’ initial match labels
- Fast Facts has a strong content/purpose match in Highlight List with Text, although the layout and icon styles still need composition.
- Alerts exist in both source and destination; the destination’s “no legacy equivalent” label conflicts with the source inventory. Severity/icon parity is still partial.
- SOURCE news keeps the feed purpose, but custom legacy queries need verification. Generic Content Query is for local posts.
- Gallery should generally map to core Gallery before Slider. A grid/lightbox and sequential carousel are different experiences.
- Table, Headline group and RDC Quote need additional work for shared references, multi-part headings and optional images; single-block matches do not capture every field.
- Shortcodes need their plugins or maintained integrations. A Custom HTML block does not implement a legacy shortcode or load its script automatically.
What the visual review can establish
The rendered static examples show layout, relative emphasis, repeated content shape and intended purpose. They support the recommendations in the catalog. Live feeds, per-site inheritance, navigation context, editing experience, form submission and responsive/accessibility behavior still need testing in WordPress.
The original legacy FPO raster assets contain damaged bytes and fail to render. New preview files use labeled substitute placeholders to make image geometry legible. Standard callout previews restore the left/right layout modifiers from the bundled CSS, and RDC previews restore the theme body class; these repairs apply to the extracted guides and generated previews. Backups of the supplied examples are retained separately; installed WordPress themes were not changed. FYE preview images remain the guide’s sample images, and labels-only entries have no fabricated screenshot. Previews now load when their comparison opens, report their full content height, and offer a direct link to the complete example.
Recommended pilot: a Standard page with sidebar, a landing page with all major slabs, a directory/bio pair, and an RDC homepage/equipment workflow. Compare content completeness, link destinations, image captions, behavior and shared updates before bulk migration.