Content model

Build directories around records, not rigid listing templates

Create collections for tools, companies, jobs, places, vendors, resources, or any other content your directory needs. DirectoryCraft counts records across collections, so your plan reflects the real content inside your site.

CollectionsRecordsCustom fields

How content works

Use structured collections instead of cramming every idea into one listing type.

Flexible fields for every collection
Reference related records
Record limits that match real site content
Create any collection
Model tools, companies, jobs, places, resources, or vendors with fields that fit the niche.
Keep records structured
Store content as clean records so browsing, filtering, imports, and public pages stay consistent.
Connect related content
Use reference-style relationships to link records across collections when your directory needs depth.

Why it matters

A serious directory rarely stays as one flat list. You need a content model that can grow with the site.

Why teams pick DirectoryCraft
Launch simple, then add richer collections as the directory grows
Keep records consistent across manual entry, CSV imports, and submissions
Create richer public pages because your data is structured from the start

Examples

Example collection setups

AI tools directory: Tools, categories, founders, pricing plans
Local guide: Places, neighborhoods, events, business owners
Job board: Jobs, companies, locations, benefits

FAQ

Questions about collections & records

What is a record?
A record is an item inside a collection. For example, one tool in a tools collection or one company in a companies collection.
Are records different from old listings?
Yes. DirectoryCraft now treats content as collection records, which gives you more flexible site structures.
Can each collection have its own fields?
Yes. Each collection can have fields that match the content you are publishing.