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

Purpose and context

A written proposal can describe an intended solution. It cannot demonstrate one.

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

Resource Hub strategy falls within the Methodology and Approach category, which carries the greatest weight in the RFP’s evaluation criteria. Rather than describing the proposed information architecture in narrative form, Phoenix × StrategyArc has implemented it, so that the OCFP can assess the member experience directly rather than infer it from static wireframes.

This prototype is submitted as supporting evidence alongside the written response. It is intended to be used by the evaluation committee, not merely reviewed.

What this prototype demonstrates

Faceted discovery

Content is classified according to how members search for it rather than according to how it was produced. Each resource remains reachable through several distinct paths rather than residing in a single fixed category.

Content as structured data

Every resource is held as a record with defined fields rather than as an individually formatted page. That structure is what makes filtering, reuse, automated surfacing, and editorial governance possible.

State rather than duplication

Live, upcoming, and on-demand are treated as states of a single content type rather than as separate libraries. A webinar therefore moves from scheduled event to archived recording without staff re-entering the record.

Accessibility as a build constraint

Semantic structure, keyboard navigation, and contrast decisions were determined during development rather than assessed after the interface was complete.

Implemented scope

Search and filtering

  • Full-text instant search across titles, descriptions, topics, and presenters
  • Five independent filter groups: Format, Topic, Audience, Availability, Certification
  • OR logic applied within each group, AND logic applied across groups
  • Result count updating live as filter selections change
  • Active filter indicators with individual and bulk removal
  • Context-aware empty state with a reset control

Content and navigation

  • 24 resource records across 7 formats and 10 clinical topics
  • Individual detail pages for every resource
  • Related resources surfaced automatically from shared topics
  • Review and expiry dates recorded on every resource
  • Mainpro+ credit values displayed where applicable
  • Featured resources pinned to the landing page

State and shareability

  • Filter and search state synchronized to URL parameters
  • Every filtered view can be distributed as a direct link
  • Browser history navigation preserved across filter changes

Accessibility

  • Skip-to-content link as the first focusable element
  • Semantic landmarks with a single H1 per page
  • ARIA live regions announcing result and filter count changes
  • Filter controls with explicit label associations
  • Visible focus states exceeding browser defaults
  • 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
  • Layout verified at 375px, 768px, and 1440px
Defined scope

Deliberate exclusions

The boundaries of this prototype were established deliberately. The following capabilities are excluded by design rather than by oversight.

  • The CMS editing interface

    This prototype presents the member-facing experience. It does not present the administrative interface OCFP staff would use to add, tag, or archive a resource. That interface is a Phase 3 deliverable to be built in WordPress, and a simulated version 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 as live connections. Integration documentation is provided to shortlisted vendors, so the proposed approach is set out in Section 3.6 of the written response rather than assumed here.

  • Enhanced search infrastructure

    Search in this prototype operates client-side across 24 records. A production library of several hundred resources requires indexed full-text search with result weighting and synonym handling, so that clinical terminology and plain-language equivalents both return accurate results. That infrastructure is scoped in the proposal and is not a requirement at prototype scale.

  • A validated taxonomy

    The facet structure, topic list, and audience categories presented here constitute a proposal rather than a conclusion. Final classification is to be confirmed through card sorting with OCFP members during Phase 2. Should members organize this content differently, the structure will be revised accordingly; identifying such differences is the purpose of conducting the exercise.

Content model and governance

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

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

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

Proposal prototype

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

Contact the project team