Suggested additions, with evidence

Section navigation

Keep orientation within a department or section when the legacy page tree is still required.

A static preview cannot prove tree generation. The need also follows the source Sidebar Nav Settings fields. A curated header menu is sufficient if automatic hierarchy is deliberately retired.

Ready when: Changing page hierarchy updates the navigation; current-page state and direct child links work on desktop and mobile.

Standard and Academic Unit page layouts

Provide a consistent home for section navigation, main content and related/contact content.

The source is a schematic, not a live page capture. Build these layouts only if sidebars are retained; a deliberate single-column redesign can use existing blocks.

Ready when: Contact/related content stays in its intended region, navigation remains contextual, and the mobile sequence is agreed and consistent.

Academic Unit layout evidence ↗

People directory and biography pages

Preserve people search, filtering, contact information and direct biography links.

Choose either a maintained external integration or a local people content type before building. The source demo is schematic; sample FYE filters do not prove runtime parity.

Ready when: Search and filters return the intended people; contact links, data refresh and direct bio URLs continue working.

RDC equipment booking and submission

Keep equipment availability, booking and submission connected to the actual service.

The inventory contains variants and dated files, not proof of 42 active workflows. Audit active usage and retain a supported service integration; a new booking engine is not implied.

Ready when: Each equipment selection reaches the correct service; a test booking/submission and confirmation complete successfully.

Tabs and modal dialogs

Preserve these interactions where they serve a real page requirement.

Verify actual use first. Inspect Sticky Nav Item’s tab layout before commissioning a new tab component. The guide-only source sample does not prove historical runtime behavior.

Ready when: Tabs have keyboard navigation and selected state; dialogs support dismissal and return focus; accordion content remains accessible.

Filmstrip

Preserve the complete introduction, action and multi-image row in one consistent composition.

Ready when: Authors can replace copy and images without rebuilding the layout; image count, captions and actions survive conversion.

Fast Facts

Make repeated numerical facts easy to author with consistent labels and optional icons.

Existing Columns, Heading and Image blocks can implement this. A dedicated block is justified only if usage and structured editing needs warrant it.

Ready when: Numbers, qualifiers, labels and icons remain paired; authors can update values without breaking the presentation.

Contact information

Avoid rebuilding the same dense contact information differently on every page.

Use a synced pattern when updates should propagate. Add a dedicated contact block only if field validation or centrally managed contacts are required.

Ready when: Phone/email links work and shared updates reach the intended pages. The card fits the chosen sidebar or main-flow layout.

Quote with portrait

Keep a quotation, attribution and optional portrait together.

The supplied RDC example is text-only. The portrait need comes from documented component options, not a visible portrait in this sample.

Ready when: Portrait, quote and attribution stay together; linked citations and mobile reading order are preserved.

RDC video hero

Support an introductory video only where retaining it is important.

Both samples illustrate image states. This is a documented capability gap, not visual proof of missing video playback. An image-only hero can use existing FYE headers.

Ready when: The hero retains one logical page title, readable actions and a usable static fallback; video behavior is checked in WordPress.

Gallery masonry and enlargement

Retain masonry and image enlargement if those are required parts of the experience.

If a regular grid is acceptable, use Gallery directly. Slider changes the browsing experience and is not a masonry replacement.

Ready when: Image ordering, captions and keyboard enlargement behavior work. Check WordPress Gallery enlargement support before adding another dependency.

Full calendars and event submission

Preserve full calendar controls or event submission separately from event teasers.

There is no rendered source calendar in this extraction. Evaluate actual embedded services before choosing the integration.

Ready when: The intended calendar, filters and submission destination work; event teaser cards continue using the existing Trumba Events block.