Adding Resource Search to freestanding websites (back)

Greg Van de Mosselaer (2024-03-27)

We have over the last year begun enhancing our resource aggregation offerings on and based on previous work on We needed something that could beat out the previous two-second RoR Load time. Enter NextJS and Fuse.js. The work took only half a day to build. It takes less than a second to load generally. Here it is...
This ability to work through the lifecycle of grabbing and vetting content, and applying the correct taxonomy, on cuts down the complexity and duplication.  Then we send it down to an affiliate site.  This creates a hub and spoke model where the existing main site (in this case; or curates the content and selectively delivers it to completely freestanding external websites and suppling them with targeted information such as medical resources that apply to the particular region or subject domain their members belong to.

In the example of on a go-forward basis this new resources page will show...

Mississauga & Local RHA & Central RHA & Ontario & Canada & International regionally scoped content 
while correctly omitting  Ottawa, Belleville, Hamilton etc scoped content.
This cuts down the signal-to-noise ratio as a health care worker because the architecture allows content brokers to... 
a) reuse their valuable links and resources for other regional sites while
b) not showing out-of-region options to EBM users that do not apply to them
... by design.

As a further offshoot of this; and can share content that exists in common. For example, if there is an international stroke website that is universally useful to primary care why not list this resource on both and keep it in sync automatically in the backend? This capacity now exists and no we did not use AI to achieve it :)