Put it into practice
Write the question each field answers. Require the fields needed to identify, classify, and contact or visit the listing; leave secondary detail optional.
What this looks like
An integration listing may need product name, supported task, documentation URL, and connection type. A team-size field may add little to that decision.
Before you move on
Could a visitor understand the listing with only the required fields completed?
Write down the evidence for your answer. If you cannot point to a concrete example, revise the work before treating it as ready.
A repeatable workflow
- Choose a representative set of listings.
- Record the source and meaning of each field.
- Review the public result before applying changes widely.
Your working notes
Apply this guide to one real project. Notes stay in this page until you download them; they are not saved to your account.
Where Directoryz fits
Directoryz supports directory publishing, listings and custom fields, CSV imports, submission review, and workspace operations. These guides include editorial workflows you can carry out with a worksheet or your own tools. They do not imply that every audit, reminder, verification, or integration is automated by Directoryz.
Foundations and templates →