FIELD GUIDE / PUBLIC RESOURCE ORGANIZATION
CATEGORY DESIGN FIELD GUIDE
How to Organize Overlapping Web Resources Without Duplicating Every Link The cleanest way to organize resources that fit several categories is to give each item one primary home and add lightweight cross-references wherever another reader might reasonably look. This preserves a single record to maintain while still supporting multiple ways of finding it. Categories should represent reader tasks, not every characteristic a resource happens to have.
PRIMARY HOME
CROSS-REFERENCES
RETRIEVAL TESTS
Prepared 20 August 2026
ONE HOME, MANY FINDERS
Guide at a glance This guide is for public link collections, shared resource libraries, team directories, learning hubs, and any index in which one destination could belong in two or more sections. It focuses on the difficult middle ground between rigid folders and uncontrolled duplication.
01 Why overlap becomes a maintenance problem 02 Use the “one home, many finders” model 03 Define categories as reader questions 04 Write a category contract 05 Choose the primary home with three tests 06 Add cross-references only for real alternate intent 07 Keep names stable across categories 08 Build an overlap matrix before publishing 09 Use external collections as comparison input 10 Test retrieval with realistic scenarios 11 Update the canonical entry, then inspect its finders 12 Final category-quality checklist
Core operating rule: one maintained entry owns the destination; alternate categories provide finders, not duplicate records.
Why overlap becomes a maintenance problem Consider a public calculator that helps freelancers estimate project time, compare rates, and generate a client summary. It could fit under Finance, Planning, Freelance Work, Client Tools, or Templates. Placing a full copy in every category appears helpful at first, but each copy can develop a different title, description, status, or destination. The problem grows quietly: - editors fix one copy but miss the others; - readers cannot tell whether similar entries are separate tools; - category totals become inflated; - broken links remain hidden in secondary sections; - search and filtering return repeated results; - ownership becomes unclear. The opposite extreme is also weak. If the calculator appears only under Finance, a reader approaching it as a planning tool may never find it. Good organization must support several discovery paths without creating several independent records.
2
ONE HOME, MANY FINDERS
Use the “one home, many finders” model Separate the place where an item is maintained from the places where it can be discovered. - Primary home: the single canonical entry containing the destination, title, description, owner, review status, and change history. - Cross-reference: a short pointer in another category that names the resource and sends the reader to its primary entry. - Search terms: alternate words or phrases that help the item appear in search without changing its category. - Related group: a temporary collection built around a task, audience, or event without moving the canonical entry. Only the primary home owns the actual destination. Cross-references should not carry their own independent copy of the link, review date, or description when the publishing system allows a pointer instead. In a static document, use a short note such as “See Planning: Project Time Estimator.” In a database or content system, reference the same record ID from several views. The implementation changes, but the ownership rule stays the same.
Define categories as reader questions A category becomes clearer when it answers a recognizable question. Compare these labels: Weak label
Reader question behind a stronger category
Miscellaneous tools
What can I use to complete a small task quickly?
Information
Where can I understand a topic before acting?
Services
Where can I submit, request, reserve, or manage something?
Community
Where can I discuss, collaborate, or get peer help?
Updates
Where can I check a changing status or announcement?
The category name can remain short, but editors should keep the reader question in an internal category contract. When an item overlaps, ask which question its main page answers most directly. Avoid creating categories from surface traits such as “has video,” “mobile friendly,” or “popular.” Those are usually filters or attributes. A resource can change those traits without changing its main purpose.
Write a category contract Before sorting items, give every major category a four-line contract: Category: Planning Includes: resources that help a reader choose steps, timing, or priorities Excludes: resources used mainly to perform the final transaction Border case: a calculator belongs here when its main output is a plan
Contracts prevent editors from relying on intuition alone. They also expose categories that are too broad. If the inclusion rule uses several unrelated verbs, split the category or clarify its scope. Keep exclusion rules concrete. “Not relevant” is not useful. “Exclude pages whose main action is purchasing or account management” gives an editor a test they can repeat.
3
ONE HOME, MANY FINDERS
Choose the primary home with three tests When an item fits multiple categories, apply these tests in order.
1. Main-task test What is the single most important action a typical reader completes at the destination? A tutorial explains; a calculator estimates; a directory locates; a form submits. Use the main action, not the number of features.
2. Entry-page test What does the linked page itself do? Do not classify an entire organization when the link points to one specific page. A university website may belong broadly to Education, while its public room-booking page belongs under Reservations.
3. Expectation test In which category would a reader be least surprised to find this exact destination? If two categories remain equally plausible, choose the one with the narrower promise as the primary home and add a cross-reference from the broader category. Record the decision in one sentence. For example: “Primary home: Planning, because the linked page produces a project schedule; cross-reference from Finance because rate inputs affect the estimate.”
Add cross-references only for real alternate intent Not every possible association deserves a pointer. Add one when a meaningful group of readers would start from a different task and still benefit from the resource. A useful cross-reference has three parts: 1. the resource name; 2. the reason it is relevant in this category; 3. the primary category where the maintained entry lives. Example: “Project Time Estimator - useful when comparing workload with rate targets; maintained under Planning.” Do not add cross-references merely to make every category look full. A pointer should solve a discovery problem. If readers are unlikely to look there, the pointer becomes clutter. Set a practical limit. One primary home plus one or two strong cross-references is enough for most resources. Items that appear to need five pointers usually reveal a category system built from overlapping nouns rather than reader tasks.
Keep names stable across categories The same resource should keep the same base name wherever it appears. Vary the explanation, not the identity. Good pattern: - Primary: “Project Time Estimator” - Cross-reference: “Project Time Estimator - compare planned hours with budget assumptions” Confusing pattern: - Primary: “Freelance Project Planner”
4
ONE HOME, MANY FINDERS
- Cross-reference: “Rate and Profit Calculator” The second pattern makes one resource look like two. If a destination genuinely performs two independent jobs, consider linking to two specific subpages instead of renaming the same general page.
Build an overlap matrix before publishing For a collection with many entries, create a temporary matrix. Rows are resources, columns are categories, and each cell receives one of three marks: - P: primary home; - X: justified cross-reference; - blank: no meaningful placement. Scan the matrix for problems: - a row with no P has no owner; - a row with multiple Ps creates duplicate maintenance; - a row filled with X marks may be too broadly described; - a column with mostly X marks may not be a real category; - two columns with nearly identical marks may need clearer contracts. The matrix is a planning tool, not something readers need to see. Its purpose is to make editorial choices explicit before the public collection becomes large.
Use external collections as comparison input An outside directory can help you observe how another publisher groups similar material, but it should not determine your categories automatically. For example, an anchor such as 주소온길 분야별 링크모음 살펴보기 combines its brand name with the original keyword 링크모음 and a category-oriented description. Treat the linked collection as one reference point, then test whether its groupings match your readers’ tasks, scope, and vocabulary. Do not copy category labels without examining what they include. Two collections may use the same label for different purposes. Likewise, a useful category in a broad public directory may be unnecessary in a small team library.
Test retrieval with realistic scenarios Editors often review a collection from the top down because they already know where everything is. Test it with short reader scenarios instead. Give a reviewer a task without naming the category: - “Find a resource that helps estimate how long a project will take.” - “Find the place to ask peers for feedback.” - “Find current instructions before submitting a request.” Observe the first category they choose, whether the resource is visible there, and whether the cross-reference makes sense. Do not help during the test. Confusion is evidence about the labels or contracts. Test at least one scenario for every major category and one scenario for a known border case. If reviewers repeatedly choose the same unexpected category, reconsider the primary home instead of adding more pointers indefinitely.
5
ONE HOME, MANY FINDERS
Update the canonical entry, then inspect its finders When a destination, title, or status changes, edit the primary entry first. Then review every cross-reference for wording that may have become inaccurate. Maintain a compact record: Canonical entry: Project Time Estimator Primary category: Planning Cross-references: Finance; Freelance Work Main task: produces a project schedule Owner: resource-library editor Last reviewed: 20 August 2026 Review trigger: main output or access conditions change
This record makes a move easier. If the resource’s main task changes from planning to invoice generation, the editor can reconsider the primary category and update two known finders instead of searching the entire collection.
Final category-quality checklist Before publishing the collection, confirm: [ ] Every category answers a distinct reader question. [ ] Every major category has an inclusion and exclusion rule. [ ] Every resource has exactly one primary home. [ ] The primary home is based on the linked page’s main task. [ ] Cross-references represent real alternate reader intent. [ ] Most resources have no more than two cross-references. [ ] Base names stay consistent wherever a resource appears. [ ] Only the canonical entry owns the destination and review status. [ ] Border cases have a one-sentence placement reason. [ ] Retrieval tests include both obvious and overlapping resources. [ ] External collections are treated as references, not templates to copy. [ ] Change records identify every finder that may need review. A category system is successful when readers can approach from different intentions while editors still maintain one reliable record. Give each resource a clear home, create only the finders that solve genuine discovery problems, and let category contracts carry the difficult decisions. The result is easier to browse today and far easier to repair later.
6