A useful resource page helps someone choose a next step. It is more than a long list of links arranged under a broad heading. The editor's work is to define the audience, explain why each item belongs and maintain the collection as sources change. A short page with clear boundaries can be more valuable than an impressive directory that gives every visitor the same unexplained options.
Define a specific reader and task
Begin with a sentence describing who the page is for and what it helps them do. For example, a first-time workshop organiser needs a different set of resources from an experienced trainer comparing evaluation methods. Narrowing the audience makes selection easier and gives readers a quick way to decide whether the page is relevant.
Write down what you will leave out. A resource page about accessible event registration does not need to become a complete guide to event management. Clear exclusions keep the collection coherent and prevent every new discovery from becoming another link. You can create a separate page when a different task develops enough material of its own.
Choose resources by role
Select items that do different jobs: an introduction, an authoritative reference, a practical tool and a place for further questions. Several interchangeable beginner articles can make a page longer without broadening its usefulness. If you include alternatives, explain the distinction that would help someone choose between them.
Prefer direct links to the relevant document or section instead of dropping readers at a large homepage. Check the page in a new session to see whether access requires an account, payment or a particular location. Mention important restrictions before the reader clicks so the next step is predictable rather than frustrating.
Write annotations that answer a question
For each resource, explain what it contains, who it suits and one limitation that matters. Avoid generic descriptions such as excellent website or lots of useful information. A note saying that a guide includes a printable checklist but focuses on small in-person events gives the reader an actual basis for choosing it.
Keep the publisher and format visible. A government reference, a volunteer-maintained tool and a commercial tutorial have different contexts. You do not need to rank them all on one scale. Explain the function of each item and allow readers to understand why a source is appropriate for the particular purpose you assign to it.
Arrange the page around a workflow
Order sections in the sequence a reader is likely to need them: understand the basics, make a plan, do the work and review the result. Alphabetical order can be useful in a directory of names, but it may be less helpful for a practical learning path. Choose the organising principle that fits the reader's task.
Use descriptive headings and link text rather than repeated click here labels. A reader scanning the page or navigating with assistive technology should be able to understand the structure. Keep annotations concise enough to compare while giving enough information to distinguish the resources. The layout should support decisions, not hide them under oversized decorative cards.
Assign maintenance and remove weak links
Record when the resources were checked and who is responsible for the next review. Prioritise links with changing information, such as software instructions or active programmes. A page can remain valuable for years if its scope is stable and its fragile details are maintained, but a date alone is not a substitute for checking the actual destinations.
Invite focused corrections, such as a broken address or a resource that no longer matches its description. Review suggestions against the same selection criteria you used at the beginning. Declining an irrelevant addition protects the page's purpose. Curation is the ongoing work of choosing and explaining, not simply allowing the list to grow.
Further reading: W3C WAI: Headings and page structure
