A resource library page that people can still find things in
Resource pages start as a tidy list of ten links and end as a wall of two hundred that nobody can search. The fix is structure: decide what kinds of resource you hold and what topics they cover, give every item the same fields, and keep them in a collection so each has its own page. Then the library can grow without collapsing.
Who uses a resource library
Charities publish toolkits for volunteers, agencies publish templates for prospects, membership bodies publish guidance for members, teachers publish worksheets for colleagues. In every case the visitor arrives with a specific need ("a risk assessment template for a community event") and a little patience. A resource hub website succeeds when that person finds the right item in two clicks and can tell at a glance whether it's current and suitable.
Two fields do most of the work: type and topic
Every item has a type (what it is) and a topic (what it's about). Keep both lists short and fixed, and write them down before you add anything.
| Types | Topics |
|---|---|
| Guide | Fundraising |
| Template | Volunteers |
| Checklist | Events |
| Video | Safeguarding |
| External link | Governance |
On a resource library page, five to eight of each is plenty. If you're tempted to add a twelfth topic, it's probably a sub-topic of one you have. Readers browsing by topic should see a list short enough to scan.
Every item, the same fields
In Anticode, keep resources in a CMS collection with typed fields, edited in the dashboard. Each item is served as its own page at /<collection>/<slug>, and the collection page lists everything. Giving each resource a page of its own, rather than just a link in a list, lets you explain what it is, who it's for and how to use it, which is also what makes it findable in search.
- Title
- What it is, in the words a searcher would use: "Event risk assessment template".
- Type and topic
- From your fixed lists.
- Summary
- One or two sentences on what it helps with and who it's for.
- How to use it
- A short paragraph or a few steps.
- Link
- Where the file or outside resource lives.
- Last reviewed
- A date. Guidance goes stale; readers need to know.
- Audience or level
- Beginner, experienced, staff only, for example.
Files themselves need a home: Anticode forms don't handle uploads and the collection holds the description, so put templates and PDFs in a shared drive or document store and link to them from each item's page. Make sure the link opens without a sign-in for the people you're publishing for.
Organising the index
- Lead with the most-used items. A "start here" section of five resources serves most visitors.
- Group the rest by topic, with the type shown on each item.
- Split into several collections if one topic grows large, so each has its own index page.
- Say what's new. A short "added recently" list at the top tells returning visitors the library is alive.
Published pages run no scripts, so there's no live filter or search box on the page. Good grouping and clear titles do the job for libraries of a few hundred items; beyond that, most visitors arrive from search engines straight to the item's page anyway.
Gated or free?
Asking for an email before a download can build a list, but it costs you most of the people who'd have used the resource and shared it. For a public-benefit toolkit, keep it free. If you want to stay in touch, put a newsletter form (it asks only for an email) on each item's page as an option. Note that Anticode doesn't deliver files after a form is sent; a gated download needs a separate tool, and the lead magnet page guide covers that route.
Building it
Describe the library: "a free resources page for a small charity network, with a resources collection by type and topic, a start-here section and a newsletter sign-up". The Architect shows a plan before building. The Technical (IBM Plex Sans) and Swiss (Inter Tight) design systems handle dense, scannable lists well; Organic (Figtree) suits a friendlier community toolkit.
Limits
- No file hosting for downloads from forms or the collection; link to files stored elsewhere.
- No member-only resources. Every published page is public.
- No live search or filtering on the page.
- No usage counts per file. Page views per page are in the dashboard; downloads are counted wherever the files live.
Questions people ask
How often should resources be reviewed?
At least yearly, and whenever rules or guidance change. Update the "last reviewed" date each time.
Can visitors suggest resources?
Yes, through the contact form or a custom form with fields for the link and topic. You add the ones you approve.
Should external links be in the library?
Yes, if they're the best resource on the topic. Mark them as external so readers know they're leaving your site.