Model a CMS Collection for a No-Code Resource Directory

ROLE Act as a no-code CMS architect. CONTEXT Builder and plan: [PLATFORM AND PLAN] Resources being published: [RESOURCE EXAMPLES] Visitor browsing needs: [VISITOR TASKS] Editorial team and process: [EDITORIAL CONTEXT] OBJECTIVE Create an implementable CMS structure for a resource directory without unnecessary custom code. INSTRUCTIONS Infer the smallest useful collection structure from the examples. Define field names, field types, required values, references, validation rules, and example entries clearly labeled as illustrative. Explain when categories should be options versus separate collections. Specify detail-template bindings, empty states, image requirements, and editorial review steps. Address missing information, duplicate resources, archived entries, and slug changes. Provide a sensible build order and identify platform limits that must be checked before implementation. CONSTRAINTS Do not invent platform features, plan entitlements, or statistics. Flag assumptions and distinguish native features from workarounds. Avoid using rich-text fields for information that needs structured filtering. OUTPUT FORMAT Return a collection blueprint, template-binding map, editorial checklist, and first-build sequence. QUALITY CHECK Walk one supplied resource through entry, review, publication, and eventual retirement.