React Resource Library

Copy Page

Most vendors publish their documentation as a flat list of PDF links. Faceting it by type, product, and language turns the same files into something a customer can actually navigate — and into a large, legitimately useful surface for search.

Installation

Props

Resource is { id, title, type, products?, language?, revision?, size?, format?, updated?, href?, gated? }. The facet lists are derived from the data — add a document with a new product or language and the filters pick it up with no extra configuration.

Details that matter on a download

Every one of the small metadata fields exists because its absence causes a support ticket:

• revision — an engineer with Rev B in their design folder needs to know at a glance whether this is newer.
• size and format — nobody wants a surprise 22 MB ZIP on a tethered connection in a lab.
• language — a localised datasheet that cannot be filtered for may as well not exist.
• gated — mark documents that require a form before the click. Springing a registration wall on someone who expected a PDF is the most reliable way to lose them, and they will not come back for the second document.

The facet counts recompute against the current search and language, but ignore the facet's own selections — the standard behaviour on distributor sites, and the reason a filter never shows you a zero-result option.

If you are filtering parts rather than documents, use Parametric Search, which composes a sortable table instead of a card list.