Skip to main content
OCFPResource Hub

Proposal Context

About this prototype

A working demonstration of the Resource Hub proposed in Phoenix × StrategyArc’s response to the OCFP 2026 Website Redesign RFP.

24
Resources
7
Formats
10
Clinical Topics
5
Filter Facets

Why this exists

Most proposals describe what a vendor would build. This one lets you use it.

The OCFP’s RFP names the Resource Hub as the flagship deliverable of the redesign: a single searchable, filterable destination consolidating self-guided learning, educational material, webinar recordings, clinical tools, and practice supports.

Resource Hub strategy sits inside the Methodology and Approach category, which carries the heaviest weight in the RFP’s evaluation criteria. Rather than describe an architecture in a document, we built it, so the OCFP can evaluate the proposed user experience directly rather than infer it from a wireframe.

What this demonstrates

Faceted discovery

Content is classified by how members look for it rather than by how it was produced. A single resource is reachable through multiple routes rather than living in one folder.

Content as structured data

Every resource is a record with defined fields, not a formatted page. This is what makes filtering, reuse, automatic surfacing, and governance possible.

State rather than duplication

Live, upcoming, and on-demand are treated as states on one content type rather than as separate libraries, so a webinar transitions from event to recording without staff re-entering it.

Accessibility as a build constraint

Semantic structure, keyboard paths, and contrast decisions were made while the interface was being built, not audited afterwards.

What is built

Search and filtering

  • Full-text instant search across titles, descriptions, topics, and presenters
  • Five independent filter groups: Format, Topic, Audience, Availability, Certification
  • OR logic within a group, AND logic across groups
  • Live result count updating as filters change
  • Active filter pills with individual removal and clear-all
  • Context-aware empty state with reset

Content and navigation

  • 24 resource records across 7 formats and 10 clinical topics
  • Individual detail pages for every resource
  • Related resource surfacing based on shared topics
  • Review and expiry dates exposed on every record
  • Mainpro+ credit values surfaced where applicable
  • Pinned featured resources on the landing page

Shareability and state

  • Filter and search state synced to URL parameters
  • Every filtered view is shareable as a link
  • Browser back and forward behave correctly across filter changes

Accessibility

  • Skip-to-content link as the first focusable element
  • Semantic landmarks and single H1 per page
  • aria-live regions announcing result and filter count changes
  • Filter controls with full label associations
  • Visible focus states beyond browser default
  • Screen-reader text on links that open in a new tab
  • No information conveyed by colour alone
  • Contrast meeting 4.5:1 for body text and 3:1 for interface elements
  • Verified at 375px, 768px, and 1440px
Scope boundary

What is deliberately not built

A prototype earns trust by being honest about its edges. The following are absent by choice, not by oversight.

  • The CMS editing interface

    The demo shows what a member sees. It does not show what OCFP staff see when adding, tagging, or archiving a resource. That interface is a Phase 3 deliverable built in WordPress, and building a convincing mock of it would demonstrate design intent rather than working capability.

  • Live integrations

    Event registration, Mainpro+ certification, and the communications platform are represented as data attributes rather than live connections. Integration documentation is shared with shortlisted vendors, so the approach is described in Section 3.6 of the proposal rather than guessed at here.

  • Enhanced search infrastructure

    Search here is client-side across 24 records. A production library of several hundred resources requires indexed full-text search with result weighting and synonym handling so clinical terminology and plain language both work. That is scoped in the proposal and is not what a 24-record prototype needs.

  • A validated taxonomy

    The facet structure, topic list, and audience categories here are our proposal, not our conclusion. Final classification is confirmed through card sorting with OCFP members in Phase 2. If members categorize this content differently than we have, the structure changes. That is the point of testing it.

Content model

The 24 records here represent a realistic content model for how OCFP staff would publish and maintain resources on the redesigned site. Each carries a format, topic tags, audience designation, availability state, Mainpro+ eligibility and credit value, a full description, and review and expiry dates.

In production this is built as structured WordPress content types with defined fields. A staff member adding a webinar recording completes a form with clear fields. The resource then appears correctly in every relevant filter automatically, and its review and expiry dates are captured at the point of creation rather than retrofitted later.

Content in this prototype is representative rather than actual. Titles and descriptions reflect the kind of material the OCFP publishes. They are not drawn from the OCFP’s live library.

Proposal prototype

This prototype was built by Phoenix in partnership with StrategyArc Inc. for the OCFP 2026 Website Redesign RFP, closing July 31, 2026. It is not affiliated with or endorsed by the Ontario College of Family Physicians.

Ask a question